aio-libs / multidict / 34938049929

87%

push

github

Store core dumps as CI artifacts on sanitizer job crashes (#1462)

## What do these changes do?

The AddressSanitizer and ThreadSanitizer jobs only print a raw hex
stack trace on a crash, with no matching binary left to symbolize it
against once the runner is gone. This enables core dumps in both jobs
and, on failure, uploads the core file together with the crashing
interpreter binary and the compiled extension as a build artifact, so
a maintainer can load them into gdb afterward instead of guessing at
offsets.

## Are there changes in behavior for the user?

No, CI-only.

## Is it a substantial burden for the maintainers to support this?

No.

## Related issue number

N/A

## Checklist

- [x] I think the code is well written
- [x] Unit tests for the changes exist -- N/A, CI-only change
- [x] Documentation reflects the changes -- N/A
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
- [x] Add a new news fragment into the `CHANGES/` folder
- [x] `make doc-spelling` passes and any new technical words are added
to `docs/spelling_wordlist.txt`

<details>
<summary>Agent run details (optional, for reviewers)</summary>

Validated the workflow YAML with `yamllint`/the GitHub Workflows
validator via `pre-commit run`, and confirmed it applies cleanly on top
of current master. Not exercised against an actual crash in this PR
(that would require deliberately breaking the build); the
artifact-upload steps are gated on `if: failure()` so they are inert on
a clean run, which is what CI will show here.

Drafted with Claude Code (Sonnet 5); reviewed by asvetlov.

</details>

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

747 of 1494 branches covered (50.0%)

Branch coverage included in aggregate %.

6133 of 6400 relevant lines covered (95.83%)

1.92 hits per line