Skip to content

gh-156939: Detect PyBytesWriter buffer overflow earlier #209196

gh-156939: Detect PyBytesWriter buffer overflow earlier

gh-156939: Detect PyBytesWriter buffer overflow earlier #209196

Triggered via pull request September 13, 2026 01:35
Status Failure
Total duration 37m 35s
Artifacts 1

build.yml

on: pull_request
Change detection  /  Create context from changed files
12s
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
Check if Autoconf files are up to date
26s
Check if Autoconf files are up to date
Check if generated files are up to date
4m 22s
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 28s
Ubuntu (installed) / build, install and test
iOS
18m 37s
iOS
Emscripten  /  build and test
15m 38s
Emscripten / build and test
WASI  /  build and test
4m 43s
WASI / build and test
Hypothesis tests on Ubuntu
9m 9s
Hypothesis tests on Ubuntu
Cross build Linux
4m 29s
Cross build Linux
Docs  /  Check EPUB
Docs / Check EPUB
Docs  /  Doctest
Docs / Doctest
Docs  /  Docs
Docs / Docs
Matrix: build-android
Docs  /  ...  /  Check for removed HTML IDs
Docs / Check for removed HTML IDs / Check for removed HTML IDs
All required checks pass
2s
All required checks pass
Fit to window
Zoom out
Zoom in

Annotations

19 errors, 7 warnings, and 2 notices
WASI / build and test
Process completed with exit code 2.
Hypothesis tests on Ubuntu
Process completed with exit code 2.
Ubuntu (free-threading) / build and test (ubuntu-26.04-arm)
Process completed with exit code 2.
macOS (free-threading) / 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)
Process completed with exit code 2.
Sanitizers / TSan
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)
Process completed with exit code 2.
Windows / Build and test (arm64, switch-case)
Process completed with exit code 2.
Windows / Build and test (x64, switch-case)
Process completed with exit code 2.
macOS / build and test (macos-26-intel)
Process completed with exit code 2.
Windows / Build and test (Win32, switch-case)
Process completed with exit code 2.
Sanitizers / TSan (free-threading)
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.
Sanitizers / UBSan
Process completed with exit code 2.
All required checks pass
Process completed with exit code 1.
Cross build Linux: Parser/lexer/string.c#L81
variable ‘previous_end’ set but not used [-Wunused-but-set-variable]
Ubuntu (installed) / build, install and test: Parser/lexer/string.c#L81
variable ‘previous_end’ set but not used [-Wunused-but-set-variable]
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 (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 / build and test (macos-26)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
Address sanitizer (ubuntu-26.04): Parser/lexer/string.c#L81
variable ‘previous_end’ set but not used [-Wunused-but-set-variable]
macOS / build and test (macos-26-intel)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
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:445307570880c3161d84d2a9376fd5812051aed259276d7a8c90364947669861