niklaslenzQwen3.8-27B in the Gauntlet
RTX 5090 32 GB · Qwentin v0.14 (kacper-daftcode), Qwen3.8-27B EXL3 5.75 bpw
What happened on the course
Each range is one task with one answer and no retry. Every wrong or missing target is a miss and costs a penalty loop. The race time is thinking, running, shooting and loops together.
| # | Task | Targets | Hits | Thinking | Buzzer | Penalty loops | Range time |
|---|---|---|---|---|---|---|---|
| 1 | River ferry (puzzle, level 1) | ✕✕✕✕✕ | 0 / 5 | 2.4 s | no | 5 (60.0 s) | 69.6 s |
| 2 | Painter (code, level 2) | ✕●●●✕ | 3 / 5 | 1.9 s | no | 2 (24.0 s) | 33.1 s |
| 3 | Bench seating (puzzle, level 3) | ●●●●● | 5 / 5 | 1.6 s | no | 0 (0.0 s) | 8.8 s |
| 4 | Snake (code, level 4) | ✕✕✕✕✕ | 0 / 5 | 6.2 s | no | 5 (75.0 s) | 88.4 s |
● hit, ✕ miss. The range time runs from arriving at the mat to leaving the range, loops included. A buzzer means the thinking cap ran out and the game forced the answer.
Every number has its file
Result (result.json) Race log (log.jsonl) Model answers (io.jsonl) System prompt Exact command Verify output Model config
Version: prompt version gauntlet-4, tasks bia-2, rules 1, prompt fingerprint 07fff686, tasks fingerprint c2c0f4f6, forced-answer style notes. Verified: the replay of the race log reproduces the end state and every code answer re-runs to the same verdict. Forced-answer style: how the game asks for the answer when the buzzer sounds (a prefilled answer start, or notes when the engine refuses that). Command and config are normalized: internal addresses appear as 127.0.0.1.
Who made what
- Qwentin engine, recipe and serve command (v0.14)kacper-daftcode (Qwentin)GitHub
- ModelQwenX @Alibaba_QwenGitHubHugging FaceWebsite
- EXL3 quantizer (exllamav3)turboderpX @turboderp_GitHubHugging Face
Full v2 results of the matching setup (same model, engine, quant and hardware; the engine build of the race is not recorded in the race files) · How the game test works · All races