aio-libs / multidict / 35189821702

87%

push

github

Disable pytest output capturing in the ASan/TSan CI jobs (#1472)

<!-- Thank you for your contribution! -->

## What do these changes do?

Runs pytest with `--capture=no` in the AddressSanitizer and
ThreadSanitizer
CI jobs. A sanitizer abort exits the process before pytest can flush its
per-test capture buffer, so the sanitizer's own report (written directly
to
fd 2) was silently dropped from the job log; only the bare exit code was
left to go on. Uncaptured output reaches the log immediately instead.

## Are there changes in behavior for the user?

No, this only affects the two sanitizer CI jobs, not published behavior.

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

No, it is a one-line flag addition to two existing job steps.

## Related issue number

N/A

## Checklist

- [x] I think the code is well written
- [ ] Unit tests for the changes exist
- [ ] Documentation reflects the changes
- [ ] 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>

Lint: `pre-commit run --files .github/workflows/ci-cd.yml
CHANGES/1472.contrib.rst` passed
Docs: `make doc-spelling` passed
YAML: validated with `yaml.safe_load`

Not run: the sanitizer jobs themselves, since reproducing them locally
needs the ASan/TSan toolchains this change targets; the diff is a flag
addition to an existing, already-passing job invocation.

</details>

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

---------

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>

747 of 1494 branches covered (50.0%)

Branch coverage included in aggregate %.

6175 of 6442 relevant lines covered (95.86%)

1.92 hits per line