Phase 2: Validate all tests with a current sanitizer runtime #618
No reviewers
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erikinkinen/AES!618
Loading…
Reference in a new issue
No description provided.
Delete branch "phase2/bug-617-current-sanitizer-runtime"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task
Closes #617
Summary
The old GCC sanitizer runtime repeatedly emitted
AddressSanitizer:DEADLYSIGNALon the Forgejo Linux 6.14 runner, although the same container passed locally. Add a separate complete Clang 19 ASan/UBSan job using a pinned official Node/Debian 13 image. Keep the ordinary GCC job and require both.Scope
Included
docs/sanitizers.md.Explicitly excluded
Design intent
Use a current sanitizer runtime and independently require the full suite to pass on the remote runner. The failure is consistent with the linked upstream old-runtime/ASLR report; the exact host entropy and causal mechanism have not been established.
Phase discipline
This is Phase 2 validation infrastructure. Instrumented timings are not research performance results. The original 45-test baseline, including archived legacy fixtures and figures, remains the gate.
Verification
The pinned Clang 19 container passed all 45 tests locally with ASan/UBSan and leak detection enabled. All repository hooks passed. Exact-head remote checks are required before merging. Local environment, logs, JUnit results and previous-run evidence are archived in the validation attachment.