Repository navigation
CI: gate main with pinned Zig unit and TSan jobs #16
Description
Activity
- added a commit that references this issue
on Jul 14, 2026 Restored the pinned Zig unit/TSan workflow on main in
a659d66. The push immediately created both remote jobs, proving the main trigger is live: https://github.com/zig-utils/zig-gc/actions/runs/29364477008Keeping this open until both jobs complete successfully.
- added a commit that references this issue
on Jul 14, 2026 The restored Linux gate exposed a real build declaration gap in https://github.com/zig-utils/zig-gc/actions/runs/29364477008:
pthread_mutex_lockwas reachable, but the test root module did not explicitly link libc. This was platform/build configuration, not allocator behavior.Fixed narrowly in
6a12d5cby settinglink_libc = trueon the shared normal/TSan test module. Localzig build testpasses. The superseding main run will verify Linux unit and 20x TSan.Superseding corrected run: https://github.com/zig-utils/zig-gc/actions/runs/29364720539
The Linux unit job is now green. The 20-iteration TSan job is in progress; the stale pre-fix run was cancelled so it would not waste a runner repeating the known missing-libc compile failure.
Completed successfully: https://github.com/zig-utils/zig-gc/actions/runs/29364720539
Both restored main-branch gates are green:
- Linux unit tests
- Linux ThreadSanitizer, 20 iterations
The workflow now runs on main pushes, pull requests, and manual dispatch.
The repository has an active
CIworkflow registered fromp7-parallel-marker, but.github/workflows/ci.ymlis absent frommain. Consequently current main pushes, including the batched allocation work in #15, receive no remote checks.Scope:
main;Acceptance:
mainstarts both jobs;