qwen2.5-coder-7b-debug-mix-GGUF

GGUF builds of Qwen/Qwen2.5-Coder-7B-Instruct fine-tuned to repair buggy Python programs (LoRA: Pilestin/qwen2.5-coder-7b-debug-mix-lora).

pass@1: 79.2 % on runtime-exception bugs (base: 73.4 %), 79.4 % overall on 946 held-out programs (untuned base model: 80.8 % overall).

File	Quant	Size
Qwen2.5-Coder-7B-Instruct.Q4_K_M.gguf	Q4_K_M	4.68 GB
Qwen2.5-Coder-7B-Instruct.Q5_K_M.gguf	Q5_K_M	5.44 GB

Usage

Ollama

The included Modelfile sets the chat template, the system prompt and the sampling parameters used in the benchmark:

hf download Pilestin/qwen2.5-coder-7b-debug-mix-GGUF --local-dir qwen2.5-coder-7b-debug-mix
cd qwen2.5-coder-7b-debug-mix
ollama create qwen2.5-coder-7b-debug-mix -f Modelfile
ollama run qwen2.5-coder-7b-debug-mix

ollama run hf.co/Pilestin/qwen2.5-coder-7b-debug-mix-GGUF:Q4_K_M also works, but then pass the system prompt yourself.

llama.cpp

llama-server -m Qwen2.5-Coder-7B-Instruct.Q4_K_M.gguf -c 4096 --temp 0

Prompt format

System prompt (use it verbatim):

You are an expert Python debugging assistant. The user gives you a buggy Python program (and optionally its runtime error and an execution trace). Reply with the corrected program in a single ```python code block. Do not add explanations.

User message. v2 (always) is the program, the failure description and the stdin; v4 appends a FocusTracer backward dynamic slice when the program raises an exception:

Fix the following buggy Python program.

```python
<buggy program>
```

Runtime error:
<exception message + last 4 lines of stderr>
   (if the program does not crash, this section is one of:
    "The program runs without crashing but produces WRONG OUTPUT for the given input."
    "The program is too slow / never terminates (time limit exceeded).")

Program input (stdin):
```
<stdin, only if ≤ 400 chars>
```
                                                         ── v2 ends here
Dynamic slice (FocusTracer, statements that led to the failure):
```
Slice criterion: exception@main.py:1
Exception: IndexError: string index out of range

Backward dynamic slice (execution order) — statements that produced this value, with the runtime values each one read:
  L1 <module>: print("A" + input()[8] + "C")  <-- CRITERION
```
                                                         ── v4 ends here

The slice is the output of FocusTracer's build_slice_context (trace recorded with detail="detailed", sliced at the exception); memory addresses are stripped and it is capped at the 30 steps nearest the crash / 2,000 characters. This is the same context FocusTracer hands to an LLM in its debugging pipeline, so the model can be dropped in there.

The reply is always the whole fixed program in one ```python block.

Evaluation

946 held-out CodeNetPy bug-fix pairs (306 problems, none seen in training). pass@1 is execution-based: the generated program is run on the problem input and its stdout is compared with the reference output. Greedy decoding (temperature 0), GGUF through Ollama on a Kaggle T4, num_ctx 4096, num_predict 1024. Paired McNemar exact tests.

Model (GGUF, Ollama)	Prompt	pass@1	runtime exception	wrong answer	time limit	exact	median latency (T4)
this model, Q4_K_M	v4	79.4 %	79.2 %	77.0 %	81.8 %	26.5 %	5.3 s
this model, Q4_K_M	v2	79.1 %	78.7 %	78.1 %	80.4 %	26.3 %	5.1 s
this model, Q5_K_M	v2	80.4 %	80.3 %	79.2 %	81.8 %	26.4 %	5.6 s
Qwen2.5-Coder-7B-Instruct (base)	v4	80.8 %	73.4 %	85.5 %	86.4 %	21.0 %	5.3 s
Qwen2.5-Coder-7B-Instruct (base)	v2	80.0 %	71.9 %	84.8 %	86.8 %	21.2 %	4.4 s
Qwen3-4B fine-tuned (sibling)	v4	75.6 %	76.2 %	73.6 %	76.4 %	24.4 %	2.8 s
Qwen2.5-3B fine-tuned (study 3)	v2	71.9 %	56.7 %	85.1 %	80.4 %	17.8 %	2.3 s

Test categories: runtime exception n = 395, wrong answer n = 269, time limit n = 280.

Paired McNemar tests against the base model (same prompt):

Comparison	overall	runtime exception	wrong answer	time limit
base → fine-tuned, v4	+84 / −97, p = 0.37	73.4 → 79.2 %, p = 0.004	85.5 → 77.0 %, p = 0.004 (worse)	86.4 → 81.8 %, p = 0.12
base → fine-tuned, v2	+91 / −100, p = 0.56	71.9 → 78.7 %, p = 0.0009	84.8 → 78.1 %, p = 0.036 (worse)	86.8 → 80.4 %, p = 0.03 (worse)
fine-tuned v2 → v4 (FocusTracer slice)	+19 / −16, p = 0.74	78.7 → 79.2 %, p = 0.83	—	—

What this means

1. The fine-tune is a runtime-exception specialist. On crashing programs it fixes +5.8 to +6.8 points more than the base model (p ≤ 0.004) — the best crash-repair rate in this study — and its fixes are closer to the reference (exact match 21 % → 26 %).
2. It is worse on non-crashing bugs. On wrong-answer and timeout bugs the base model is clearly better, so overall pass@1 is roughly equal (−1.4 points, not significant). Use this adapter when the program raises an exception, and the plain base model otherwise — the LoRA can be switched per request on the same base weights.
3. The FocusTracer slice adds little on top of the error message (+0.5 points).

Note: this harness is more generous than the one used for the earlier Qwen2.5-3B study (longer generation budget, Python 3.13), so every baseline above was re-measured here rather than copied.

Training data

The training data is not published. Summary:

• 13,682 train / 628 val chat examples (problem-disjoint), plus a held-out test set of 946 CodeNetPy pairs from 306 problems that never appear in training.
• RunBugRun (Python subset, CodeNet-derived buggy → accepted pairs with test inputs): 178,797 candidates → test problems removed, length ≤ 4,000 chars, diff ≤ 30 % of lines, ≤ 20 pairs per problem → every pair re-executed: the fix must pass the first 8 tests and the buggy version must fail at least one. 12,359 pairs survived (11,799 used in train).
• CodeNetPy (study-3 train split, 1,883 pairs).
• Categories (train): wrong answer 9,674 · runtime exception 3,323 · time limit 685.
• mix variant: 50 % of runtime-exception rows (1,655) carry the v4 FocusTracer slice, the rest use v2 — so one model serves both prompt styles.

Training procedure

Unsloth + HF Trainer, completion-only loss (prompt tokens masked), on one Kaggle T4.

Setting	Value
Base model	Qwen/Qwen2.5-Coder-7B-Instruct (4-bit NF4 QLoRA)
LoRA	r = 32, alpha = 32, rsLoRA, dropout 0, all attention + MLP projections
Max sequence length	3,072
Schedule	1 epoch (855 steps), best val-loss checkpoint kept
Effective batch	16 (2 × 8 grad. accumulation)
Optimizer / LR	AdamW 8-bit, 1e-4, cosine, 3 % warmup
Wall clock	8.3 h
Best val loss	0.0574

Limitations

• Trained on short stdin/stdout competitive-programming programs. It is not a general coding assistant and was not tested on multi-file or library code.
• It can return the input unchanged or a plausible but wrong fix — run the output.
• English prompts only; use the exact system prompt and user template above.
• Benchmarks were measured on the GGUF builds via Ollama, not on the bf16 adapter.

Links

• FocusTracer: https://github.com/BitnetTR/focustracer