Use a current sanitizer runtime on the Forgejo runner #617
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#617
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Goal
Run the full ASan/UBSan suite reliably on the Forgejo runner with a current runtime, while preserving the ordinary GCC build and all instrumentation.
Evidence
During #614 / PR #616, sanitized GCC 12 builds linked correctly but the remote tests stalled at startup. Runs 23501/23504 stopped reporting progress at the ID test. Bounded diagnostic runs 23509/23512 showed repeated
AddressSanitizer:DEADLYSIGNAL, including in the trivial smoke executable. The remote host reports Linux 6.14.0-1-pve. These failed/stalled runs were retained and then cancelled to stop the output loop.All 45 tests pass locally under Clang 22 ASan/UBSan, ordinary GCC 16 Release, and GCC 12 ASan/UBSan inside the same node:20-bookworm image. This points to a runner/runtime interaction rather than establishing an AES memory error. The pattern is consistent with the older-runtime/high-ASLR incompatibility discussed in google/sanitizers #1614; exact host ASLR settings still require read-only confirmation. LLVM reports the ASan fix in version 17.0.0.
Steps
Done
Both ordinary and sanitized suites pass with recorded compiler/runtime identities. No test, sanitizer, memory check or host address-randomization setting is disabled to obtain a pass.