submissionincorrect
#4242 spec_strategy_v6.so
Public correctness passed, but the held-out replay diverged from the reference. Latency was not measured.
Outcome
- Score
- —
- Rank
- —
- Phase
- hidden
- Uploaded
- 51m ago
- Size
- 30 KB
Pipeline
What happened, in order
Every submission runs through the same stages. Each row shows what the stage did, how long it took, and whether it passed.
- 01Uploaded30 KB138 ms
- 02Symbol checkcreate_strategy resolved41 ms
- 03Public correctnessmatched reference1.24 s
- 04Hidden correctnessorder stream diverged at tick 4,128,901 (BUY price ≠ ask)8.10 s
- 05Latency replayskipped (correctness gate)—
- 06Score publishedskipped—
What this means
Your submission drifted from the strategy spec. The first order that disagreed with the reference stream terminated the run. Re-read STRATEGY_SPEC.md and try again. You can replay the public dataset locally with the reference judge.
Ready to ship the next attempt?
Your cooldown resets in 6 minutes. Use it to inline the rolling window, or to switch the symbol map from unordered_map to a fixed array.