Skip to content

A compilation error is a verdict, not a failure to judge - #95

Merged
kisielewski merged 1 commit into
mainfrom
fix/parity-world-compilation-error
Sep 6, 2026
Merged

A compilation error is a verdict, not a failure to judge#95
kisielewski merged 1 commit into
mainfrom
fix/parity-world-compilation-error

Conversation

@kisielewski

Copy link
Copy Markdown
Member

The parity seed marked team7's compilation error failed, which is the state
an infrastructure failure leaves — the Runner never reports one for a
compilation error. compilation_failed in aj-standard-io returns
Evaluated::Judged with a score and infrastructureFailure: false, so the
Server stores it Completed with 0.

It matters now because the Client's ICPC board stops charging twenty penalty
minutes for a submission nobody returned a verdict for
(AlgoJudge/AlgoJudge-Client#…). Left as it was, this seed would have shown a
compilation error costing nothing, which is the opposite of what it costs.

Adds the row that state is actually for: team7 on D, an evaluation that
failed with the judge's message and no verdict — the shape the board draws as
?. Mirrors AlgoJudge-Client/src/api/fake/fixtures/world.ts, which the two
seeds exist to keep identical.

Seed data only. dotnet build -warnaserror clean.

The seed marked one `failed`, which is the state an infrastructure failure
leaves. Adds the case that state is actually for.
@kisielewski
kisielewski merged commit 712e962 into main Sep 6, 2026
3 checks passed
@kisielewski
kisielewski deleted the fix/parity-world-compilation-error branch September 6, 2026 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant