Home / Game / 256 GB

Game test · 256 GB · 2× DGX Spark (GB10)

GLM-5.3-Flash in the Gauntlet

2 DGX Sparks 256 GB · TensorFold native (Zig 0.17.0, engine f350cd3e + Mia's 112 patches), Mia's GLM-5.3-Flash recipe 1104 @d4226a1 (EXL3 4 bpw, DFlash2 drafts, tensor parallel 2)

season seed 21Thinking offone attempt, no helpraced Nov 10, 2026replay verified
Rank in 256 GB
6of 8
Finish time
346.3s
Targets hit
3of 20
Penalty loops
17(231.0 s)
Thinking time
34.5s
Buzzers
0
The four ranges

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.

#TaskTargetsHitsThinkingBuzzerPenalty loopsRange time
1River ferry (puzzle, level 1)✕●✕✕✕1 / 56.8 sno4 (48.0 s)62.0 s
2Painter (code, level 2)✕✕●✕✕1 / 54.2 sno4 (48.0 s)59.4 s
3Bench seating (puzzle, level 3)✕✕✕✕●1 / 56.7 sno4 (60.0 s)73.9 s
4Snake (code, level 4)✕✕✕✕✕0 / 516.9 sno5 (75.0 s)99.1 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.

Raw files

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.

Credits

Who made what

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