[3.13] gh-116946: fully implement GC protocol for _curses_panel.panel (GH-138333)
#165390
Triggered via pull request
September 3, 2025 08:53
picnixz
Status
Success
Total duration
22m 12s
Artifacts
–
build.yml
on: pull_request
Change detection
/
Create context from changed files
10s
Matrix: build-android
Matrix: Address sanitizer
Matrix: build-macos
Matrix: build-san
Matrix: Ubuntu SSL tests with OpenSSL
Matrix: build-ubuntu
Matrix: build-windows-msi
Waiting for pending jobs
Matrix: build-windows
Matrix: CIFuzz
Check if Autoconf files are up to date
31s
Check if generated files are up to date
6m 42s
WASI
/
build and test
11m 4s
Hypothesis tests on Ubuntu
8m 9s
Docs
/
Check EPUB
Docs
/
Docs
Docs
/
Doctest
Check if the ABI has changed
1m 44s
All required checks pass
2s
Annotations
14 warnings and 5 notices
|
Check if the ABI has changed
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
macOS (free-threading) / build and test (ghcr.io/cirruslabs/macos-runner:sonoma)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated
dependents or dependents with broken linkage!
|
|
macOS (free-threading) / build and test (ghcr.io/cirruslabs/macos-runner:sonoma)
xz 5.8.1 is already installed and up-to-date.
To reinstall 5.8.1, run:
brew reinstall xz
|
|
macOS (free-threading) / build and test (ghcr.io/cirruslabs/macos-runner:sonoma)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
macOS / build and test (ghcr.io/cirruslabs/macos-runner:sonoma)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated
dependents or dependents with broken linkage!
|
|
macOS / build and test (ghcr.io/cirruslabs/macos-runner:sonoma)
xz 5.8.1 is already installed and up-to-date.
To reinstall 5.8.1, run:
brew reinstall xz
|
|
macOS / build and test (ghcr.io/cirruslabs/macos-runner:sonoma)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
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.
|
|
Address sanitizer (ubuntu-24.04)
‘__builtin_strncpy’ output truncated before terminating nul copying as many bytes from a string as its length [-Wstringop-truncation]
|
|
macOS / build and test (macos-13)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated
dependents or dependents with broken linkage!
|
|
macOS / build and test (macos-13)
tcl-tk@8 8.6.17 is already installed and up-to-date.
To reinstall 8.6.17, run:
brew reinstall tcl-tk@8
|
|
macOS / build and test (macos-13)
gdbm 1.26 is already installed and up-to-date.
To reinstall 1.26, run:
brew reinstall gdbm
|
|
macOS / build and test (macos-13)
xz 5.8.1 is already installed and up-to-date.
To reinstall 5.8.1, run:
brew reinstall xz
|
|
macOS / build and test (macos-13)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
Windows (free-threading) / build (arm64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
Windows / build (arm64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
Windows / build and test (x64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
Windows / build and test (Win32)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
Windows (free-threading) / build and test (x64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|