Skip to content

gh-156939: Detect buffer overflow in PyBytesWriter in debug mode #208285

gh-156939: Detect buffer overflow in PyBytesWriter in debug mode

gh-156939: Detect buffer overflow in PyBytesWriter in debug mode #208285

Triggered via pull request September 4, 2026 15:09
Status Failure
Total duration 35m 4s
Artifacts 2

build.yml

on: pull_request
Change detection  /  Create context from changed files
11s
Change detection / Create context from changed files
Matrix: Address sanitizer
Matrix: build-macos
Matrix: build-san
Matrix: Ubuntu SSL tests
Matrix: build-ubuntu
Matrix: build-windows
Matrix: cifuzz
Docs  /  Doctest
6m 22s
Docs / Doctest
Docs  /  Check EPUB
2m 24s
Docs / Check EPUB
Check if Autoconf files are up to date
22s
Check if Autoconf files are up to date
Check if generated files are up to date
5m 3s
Check if generated files are up to date
C API Docs  /  Check if all C APIs are documented
11s
C API Docs / Check if all C APIs are documented
Ubuntu (installed)  /  build, install and test
6m 13s
Ubuntu (installed) / build, install and test
iOS
22m 44s
iOS
Emscripten  /  build and test
17m 43s
Emscripten / build and test
WASI  /  build and test
5m 14s
WASI / build and test
Hypothesis tests on Ubuntu
11m 3s
Hypothesis tests on Ubuntu
Cross build Linux
4m 52s
Cross build Linux
Matrix: build-android
Docs  /  ...  /  Check for removed HTML IDs
2m 24s
Docs / Check for removed HTML IDs / Check for removed HTML IDs
All required checks pass
3s
All required checks pass
Fit to window
Zoom out
Zoom in

Annotations

24 errors, 5 warnings, and 2 notices
Docs / Docs
Process completed with exit code 2.
Docs / Check EPUB
Process completed with exit code 1.
WASI / build and test
Process completed with exit code 2.
Ubuntu (installed) / build, install and test
Process completed with exit code 2.
Docs / Doctest
Process completed with exit code 2.
Ubuntu (bolt) / build and test (ubuntu-26.04)
Process completed with exit code 2.
Ubuntu (free-threading) / build and test (ubuntu-26.04-arm)
Process completed with exit code 2.
Hypothesis tests on Ubuntu
Process completed with exit code 2.
Windows / Build and test (x64, tail-call)
Process completed with exit code 2.
Address sanitizer (ubuntu-26.04)
Process completed with exit code 2.
Windows (free-threading) / Build and test (x64, tail-call)
Process completed with exit code 2.
macOS / build and test (macos-26)
Process completed with exit code 2.
Ubuntu / build and test (ubuntu-26.04-arm)
Process completed with exit code 2.
Ubuntu / build and test (ubuntu-26.04)
Process completed with exit code 2.
macOS / build and test (macos-26-intel)
Process completed with exit code 2.
Ubuntu (free-threading) / build and test (ubuntu-26.04)
Process completed with exit code 2.
macOS (free-threading) / build and test (macos-26)
Process completed with exit code 2.
Windows / Build and test (x64, switch-case)
Process completed with exit code 2.
Windows / Build and test (arm64, switch-case)
Process completed with exit code 2.
Windows / Build and test (Win32, switch-case)
Process completed with exit code 2.
Sanitizers / UBSan
Process completed with exit code 2.
Windows (free-threading) / Build and test (arm64, switch-case)
Process completed with exit code 2.
Windows (free-threading) / Build and test (x64, switch-case)
Process completed with exit code 2.
All required checks pass
Process completed with exit code 1.
Hypothesis tests on Ubuntu
No files were found with the provided path: /home/runner/work/cpython/cpython-builddir/.hypothesis/examples/. No artifacts will be uploaded.
macOS / build and test (macos-26)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
macOS / build and test (macos-26-intel)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
macOS (free-threading) / build and test (macos-26)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
macOS (free-threading) / build and test (macos-26)
The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust
Windows / Build and test (arm64, switch-case)
"The windows-11-arm label will migrate to use Visual Studio 2026 by default beginning September 21, 2026. For more information see https://github.com/actions/runner-images/issues/14602"
Windows (free-threading) / Build and test (arm64, switch-case)
"The windows-11-arm label will migrate to use Visual Studio 2026 by default beginning September 21, 2026. For more information see https://github.com/actions/runner-images/issues/14602"

Artifacts

Produced during runtime
Name Size Digest
UBSan-logs-default
1.59 KB
sha256:970ffaea2ccab253e93af6f56e9daf783b41be005b76907753f41a9bfc97c18b
html-ids-head.json.gz
126 KB
sha256:d5396c4b6912fc75f091aa51ab57ad914d42da290cf9bd669255f27f56f66d3d