Skip to content

fix: use safe deserialization in pickle.py #193890

fix: use safe deserialization in pickle.py

fix: use safe deserialization in pickle.py #193890

Triggered via pull request May 25, 2026 10:39
Status Failure
Total duration 26m 8s
Artifacts 1

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-msi
Waiting for pending jobs
Matrix: build-windows
Matrix: cifuzz
Waiting for pending jobs
Check if Autoconf files are up to date
23s
Check if Autoconf files are up to date
Check if generated files are up to date
4m 8s
Check if generated files are up to date
C API Docs  /  Check if all C APIs are documented
10s
C API Docs / Check if all C APIs are documented
iOS
22m 33s
iOS
Emscripten  /  build and test
18m 10s
Emscripten / build and test
WASI  /  build and test
5m 29s
WASI / build and test
Hypothesis tests on Ubuntu
10m 9s
Hypothesis tests on Ubuntu
Cross build Linux
4m 0s
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
5s
All required checks pass
Fit to window
Zoom out
Zoom in

Annotations

19 errors and 4 warnings
WASI / build and test
Process completed with exit code 2.
macOS / build and test (macos-26)
Process completed with exit code 2.
Windows / Build and test (x64, tail-call)
Process completed with exit code 2.
Ubuntu / build and test (ubuntu-24.04)
Process completed with exit code 2.
Windows (free-threading) / Build and test (x64, tail-call)
Process completed with exit code 2.
Ubuntu (free-threading) / build and test (ubuntu-24.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-24.04-arm)
Process completed with exit code 2.
Address sanitizer (ubuntu-24.04)
Process completed with exit code 2.
Windows / Build and test (Win32, switch-case)
Process completed with exit code 2.
Ubuntu (free-threading) / build and test (ubuntu-24.04)
Process completed with exit code 2.
Android (x86_64)
Process completed with exit code 1.
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.
Ubuntu (bolt) / build and test (ubuntu-24.04)
Process completed with exit code 2.
macOS / build and test (macos-26-intel)
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.
macOS / build and test (macos-26)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
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-intel)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!

Artifacts

Produced during runtime
Name Size Digest
UBSan-logs-default
1.54 KB
sha256:1a0f91feaf038126db6a9c3baef4f71965f6f8be11b4b76ac8b2b403a0d4365b