niklaslenzQwen3.8-27B in the Gauntlet
RTX 5090 32 GB · vLLM 0.31.0 with humming kernels, Kaitchup Qwen3.8-27B SLQ-EAR98
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) | ●✕✕✕● | 2 / 5 | 4.7 s | no | 3 (36.0 s) | 47.9 s |
| 2 | Painter (code, level 2) | ✕●●●✕ | 3 / 5 | 3.2 s | no | 2 (24.0 s) | 34.4 s |
| 3 | Bench seating (puzzle, level 3) | ●●●●● | 5 / 5 | 2.8 s | no | 0 (0.0 s) | 10.0 s |
| 4 | Snake (code, level 4) | ●✕●✕● | 3 / 5 | 18.2 s | no | 2 (30.0 s) | 55.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
- Quantization (SLQ EAR>98, Humming) and serve commandThe Kaitchup (Benjamin Marie)X @bnjmn_marieGitHubHugging FaceWebsite
- Base model (Qwen3.8-27B)QwenX @Alibaba_QwenGitHubHugging FaceWebsite
- Engine (vLLM)vLLMGitHub
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