Skip to content

Make it possible to use Py_Finalize before calling the PythonQt destructor #501

Make it possible to use Py_Finalize before calling the PythonQt destructor

Make it possible to use Py_Finalize before calling the PythonQt destructor #501

Triggered via pull request June 26, 2025 19:30
Status Failure
Total duration 10m 2s
Artifacts 4

build.yml

on: pull_request
Matrix: macOS
Matrix: oldschool
Matrix: ubuntu
Matrix: windows
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
oldschool (rockylinux, 9, release)
Process completed with exit code 1.
oldschool (rockylinux, 9, debug)
Process completed with exit code 1.
ubuntu (24.04)
Process completed with exit code 2.
macOS (latest, 3.11, 5.12.*, debug)
No files were found with the provided path: generated_cpp. No artifacts will be uploaded.
macOS (latest, 3.9, 5.9.*, debug)
No files were found with the provided path: generated_cpp. No artifacts will be uploaded.
macOS (latest, 3.9, 5.9.*, release)
No files were found with the provided path: generated_cpp. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size Digest
wrappers_ubuntu_22.04 Expired
1.1 MB
sha256:0eb5d2510dc4bbe7ec275327eff25d0e0109670721ed85042471be873766dcfb
wrappers_win32_mingw53_5.11 Expired
1010 KB
sha256:b7fda5e2571bf838521d815449cf2eee4e78efd805b57cd6cb778a2c622809ea
wrappers_win64_mingw73_5.12 Expired
1020 KB
sha256:40d69e56891081247eaf68f3258a6fdefa4deafd1ed57c8ad5c9ca08b232de09
wrappers_win64_msvc2017_64_5.11 Expired
1010 KB
sha256:1252c01ad08b9b4230d1d9780a21def4ad13a91a05c6a939d3a33cc5e307309e