Phase 2: Validate all tests with a current sanitizer runtime #618

Merged
erikinkinen merged 1 commit from phase2/bug-617-current-sanitizer-runtime into main 2026-10-20 17:02:59 +02:00
Owner

Task

Closes #617

Summary

The old GCC sanitizer runtime repeatedly emitted AddressSanitizer:DEADLYSIGNAL on 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

  • Full instrumented suite with leak and undefined-behavior failures enabled.
  • A 15-minute job limit, 120-second per-test limit and bounded failure output.
  • Recorded compiler/runtime versions and host ASLR value when readable.
  • Local commands and the observed runtime boundary in docs/sanitizers.md.

Explicitly excluded

  • Host ASLR changes, disabled sanitizer checks or test retries.
  • Production-code changes; transitive runtime linkage is already fixed by #616.

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.

# Task Closes #617 ## Summary The old GCC sanitizer runtime repeatedly emitted `AddressSanitizer:DEADLYSIGNAL` on 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 - Full instrumented suite with leak and undefined-behavior failures enabled. - A 15-minute job limit, 120-second per-test limit and bounded failure output. - Recorded compiler/runtime versions and host ASLR value when readable. - Local commands and the observed runtime boundary in `docs/sanitizers.md`. ### Explicitly excluded - Host ASLR changes, disabled sanitizer checks or test retries. - Production-code changes; transitive runtime linkage is already fixed by #616. ## 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](https://git.erikinkinen.fi/attachments/0434206b-0131-44d9-891c-2b9a7b892c70).
erikinkinen added this to the Phase 2 milestone 2026-10-20 16:58:19 +02:00
Phase 2: Add current Clang sanitizer CI runtime (#617)
All checks were successful
markdownlint / markdown-lint (pull_request) Successful in 16s
clang-format / check-format (pull_request) Successful in 17s
ci / sanitizers (pull_request) Successful in 3m47s
ci / smoke (pull_request) Successful in 3m49s
markdownlint / markdown-lint (push) Successful in 16s
clang-format / check-format (push) Successful in 16s
ci / sanitizers (push) Successful in 2m53s
ci / smoke (push) Successful in 2m56s
0318f857d3
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erikinkinen/AES!618
No description provided.