[Minor Feature] CI pipeline for debug-test and asan-test #285

New issue

Closed

opened 2026-03-08 03:20:09 +00:00 by john · 0 comments

john commented

2026-03-08 03:20:09 +00:00

Owner

Context

The debug build system provides make debug-test (fast, catches refcount bugs) and make asan-test (thorough, catches memory corruption). These should run automatically.

Proposal

Add a Gitea Actions workflow:

On every push: make debug-test — fast (~2 min), catches Python refcount bugs and pydebug assertion failures
Nightly or per-PR: make asan-test — slower (~3 min), catches heap overflow, use-after-free, undefined behavior
Weekly: make valgrind-test — slowest (~30 min with 50x timeout), deep memory analysis

Prerequisites

Gitea Actions runner with build dependencies installed
__lib_debug/ pre-built on the runner (or built in CI)

#279 (memory safety audit meta-issue)

## Context The debug build system provides `make debug-test` (fast, catches refcount bugs) and `make asan-test` (thorough, catches memory corruption). These should run automatically. ## Proposal Add a Gitea Actions workflow: 1. **On every push**: `make debug-test` — fast (~2 min), catches Python refcount bugs and pydebug assertion failures 2. **Nightly or per-PR**: `make asan-test` — slower (~3 min), catches heap overflow, use-after-free, undefined behavior 3. **Weekly**: `make valgrind-test` — slowest (~30 min with 50x timeout), deep memory analysis ## Prerequisites - Gitea Actions runner with build dependencies installed - `__lib_debug/` pre-built on the runner (or built in CI) ## Related - #279 (memory safety audit meta-issue)