yhirose 69d3998453 Revert ASAN detect_stack_use_after_return for #2431 repro ...

The option did not detect the bug in CI -- the resolver worker write
likely lands on the heap (via the gaicb's pai pointer) or happens after
the test process exits, neither of which stack-use-after-return can
catch. Roll back to relying on the job-level timeout: bug present ->
post-cleanup hangs ~8min then job-level timeout cancels at 10min total;
bug fixed -> job completes in ~2min.

2026-04-28 09:40:12 +09:00

..

workflows

Revert ASAN detect_stack_use_after_return for #2431 repro

2026-04-28 09:40:12 +09:00