Skip to content

gh-69371: Fix pydoc for modules whose path contains undecodable bytes #204691

gh-69371: Fix pydoc for modules whose path contains undecodable bytes

gh-69371: Fix pydoc for modules whose path contains undecodable bytes #204691

Triggered via pull request August 5, 2026 12:29
Status Failure
Total duration 48m 36s
Artifacts 2

build.yml

on: pull_request
Change detection  /  Create context from changed files
13s
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
Waiting for pending jobs
Docs  /  Doctest
9m 9s
Docs / Doctest
Docs  /  Check EPUB
2m 33s
Docs / Check EPUB
Check if Autoconf files are up to date
24s
Check if Autoconf files are up to date
Check if generated files are up to date
4m 35s
Check if generated files are up to date
C API Docs  /  Check if all C APIs are documented
9s
C API Docs / Check if all C APIs are documented
iOS
22m 0s
iOS
Emscripten  /  build and test
19m 54s
Emscripten / build and test
WASI  /  build and test
5m 10s
WASI / build and test
Hypothesis tests on Ubuntu
9m 24s
Hypothesis tests on Ubuntu
Cross build Linux
4m 42s
Cross build Linux
Matrix: build-android
Docs  /  ...  /  Check for removed HTML IDs
2m 10s
Docs / Check for removed HTML IDs / Check for removed HTML IDs
All required checks pass
4s
All required checks pass
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 5 warnings
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.
Windows / Build and test (x64, tail-call)
Process completed with exit code 2.
macOS / build and test (macos-26)
Process completed with exit code 2.
macOS (free-threading) / build and test (macos-26)
Process completed with exit code 2.
Windows (free-threading) / Build and test (x64, tail-call)
Process completed with exit code 2.
Windows / Build and test (arm64, switch-case)
Process completed with exit code 2.
iOS
Process completed with exit code 1.
Windows / Build and test (x64, switch-case)
Process completed with exit code 2.
Windows / Build and test (Win32, switch-case)
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.
macOS / build and test (macos-26-intel)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
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)
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
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

Artifacts

Produced during runtime
Name Size Digest
UBSan-logs-default
1.59 KB
sha256:2964cb92f690bf2abf2a57982c1ab77e7664f84906822aada41c58fc684d8a0c
html-ids-head.json.gz
125 KB
sha256:05a67b065971c1e31760df283b6f8bb6f49e105ff2923344f0fa2c398e3387bf