Observed at PR #631 head d811e0c2accc8997eecb5071f8752f88e9fb44e4. Failing CI job.
In #631 the Windows GNU amd64 compiler builds successfully, then the corpus step fails on one module. Because Run Rust tests follows it with the default success condition, all Rust regressions in that job are skipped, including the new native I/O harness.
The Windows ARM64 job records a timed-send failure, but we have no native Windows GNU amd64 comparison from this run even though its compiler was already built. The separate Wave Cases job passing does not execute std_io_regressions.
Scope: arrange independent post-build validation so a corpus failure does not suppress Rust runtime tests (separate dependent jobs or explicit prerequisite-aware conditions). Keep both checks mandatory and preserve the corpus failure. Do not use blanket continue-on-error or run compiler-dependent checks when setup/build failed.
Acceptance:
- Injecting a corpus-check failure after successful setup/build still records a Rust test result.
- Failed build/setup skips dependent checks with an accurate reason.
- Cancellation is respected and either validation failure still fails the job.
- No loss of current corpus/example/Rust coverage.
Related to #575, which is specifically about native ARM64 checks behind codegen diagnostics. This task is the separate Windows GNU corpus-to-Rust dependency visible in this run.
Source references:
Observed at PR #631 head
d811e0c2accc8997eecb5071f8752f88e9fb44e4. Failing CI job.In #631 the Windows GNU amd64 compiler builds successfully, then the corpus step fails on one module. Because
Run Rust testsfollows it with the default success condition, all Rust regressions in that job are skipped, including the new native I/O harness.The Windows ARM64 job records a timed-send failure, but we have no native Windows GNU amd64 comparison from this run even though its compiler was already built. The separate Wave Cases job passing does not execute
std_io_regressions.Scope: arrange independent post-build validation so a corpus failure does not suppress Rust runtime tests (separate dependent jobs or explicit prerequisite-aware conditions). Keep both checks mandatory and preserve the corpus failure. Do not use blanket continue-on-error or run compiler-dependent checks when setup/build failed.
Acceptance:
Related to #575, which is specifically about native ARM64 checks behind codegen diagnostics. This task is the separate Windows GNU corpus-to-Rust dependency visible in this run.
Source references: