Skip to content

CI: Use a Ubuntu 20.04 container to keep Ubuntu 20.04 support #1969

CI: Use a Ubuntu 20.04 container to keep Ubuntu 20.04 support

CI: Use a Ubuntu 20.04 container to keep Ubuntu 20.04 support #1969

Triggered via pull request June 4, 2025 18:23
Status Cancelled
Total duration 3m 4s
Artifacts 1

test-and-publish.yaml

on: pull_request
Matrix: build-spidermonkey-unix
build-spidermonkey-win
11s
build-spidermonkey-win
Matrix: build-and-test
publish
0s
publish
publish-archive
0s
publish-archive
publish-nightly
0s
publish-nightly
Fit to window
Zoom out
Zoom in

Annotations

68 errors and 26 warnings
build-and-test (ubuntu-22.04, 3.9)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.9)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.9)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.9)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build-and-test (ubuntu-22.04, 3.13)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.13)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.13)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.13)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
build-and-test (ubuntu-22.04, 3.10)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.10)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.10)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.10)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build-and-test (ubuntu-22.04, 3.8)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.8)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.8)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.8)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build-and-test (ubuntu-22.04, 3.12)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.12)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.12)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.12)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
build-and-test (ubuntu-22.04, 3.11)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.11)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.11)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.11)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build-and-test (macos-13, 3.13)
The run was canceled by @Xmader.
build-and-test (macos-14, 3.12)
The run was canceled by @Xmader.
build-and-test (macos-14, 3.10)
The run was canceled by @Xmader.
build-and-test (macos-14, 3.11)
The run was canceled by @Xmader.
build-and-test (macos-14, 3.9)
The run was canceled by @Xmader.
build-and-test (macos-14, 3.8)
The run was canceled by @Xmader.
build-and-test (macos-14, 3.13)
The run was canceled by @Xmader.
build-and-test (ubuntu-22.04-arm, 3.8)
The run was canceled by @Xmader.
build-and-test (ubuntu-22.04-arm, 3.10)
The run was canceled by @Xmader.
build-and-test (ubuntu-22.04-arm, 3.13)
The run was canceled by @Xmader.
build-and-test (ubuntu-22.04-arm, 3.11)
The operation was canceled.
build-and-test (ubuntu-22.04-arm, 3.11)
The run was canceled by @Xmader.
build-and-test (ubuntu-22.04-arm, 3.9)
The operation was canceled.
build-and-test (ubuntu-22.04-arm, 3.9)
The run was canceled by @Xmader.
build-and-test (windows-2022, 3.12)
The operation was canceled.
build-and-test (windows-2022, 3.9)
The operation was canceled.
build-and-test (windows-2022, 3.9)
The run was canceled by @Xmader.
build-and-test (windows-2022, 3.12)
The run was canceled by @Xmader.
build-and-test (windows-2022, 3.8)
The operation was canceled.
build-and-test (windows-2022, 3.8)
The run was canceled by @Xmader.
build-and-test (windows-2022, 3.10)
The operation was canceled.
build-and-test (windows-2022, 3.10)
The run was canceled by @Xmader.
build-and-test (macos-13, 3.11)
The operation was canceled.
build-and-test (macos-13, 3.11)
cmake 3.31.6 is already installed To upgrade to 4.0.2, run: brew upgrade cmake
build-and-test (macos-13, 3.11)
The run was canceled by @Xmader.
build-and-test (ubuntu-22.04-arm, 3.12)
The operation was canceled.
build-and-test (ubuntu-22.04-arm, 3.12)
The run was canceled by @Xmader.
build-and-test (macos-13, 3.10)
The operation was canceled.
build-and-test (macos-13, 3.10)
cmake 3.31.6 is already installed To upgrade to 4.0.2, run: brew upgrade cmake
build-and-test (macos-13, 3.10)
The run was canceled by @Xmader.
build-and-test (windows-2022, 3.13)
The operation was canceled.
build-and-test (windows-2022, 3.13)
The run was canceled by @Xmader.
build-and-test (windows-2022, 3.11)
The operation was canceled.
build-and-test (windows-2022, 3.11)
The run was canceled by @Xmader.
build-and-test (macos-13, 3.9)
The operation was canceled.
build-and-test (macos-13, 3.9)
cmake 3.31.6 is already installed To upgrade to 4.0.2, run: brew upgrade cmake
build-and-test (macos-13, 3.9)
The run was canceled by @Xmader.
build-and-test (macos-13, 3.12)
The operation was canceled.
build-and-test (macos-13, 3.12)
cmake 3.31.6 is already installed To upgrade to 4.0.2, run: brew upgrade cmake
build-and-test (macos-13, 3.12)
The run was canceled by @Xmader.
Test and Publish Suite
The run was canceled by @Xmader.
build-and-test (macos-13, 3.8)
The operation was canceled.
build-and-test (macos-13, 3.8)
cmake 3.31.6 is already installed To upgrade to 4.0.2, run: brew upgrade cmake
build-and-test (macos-13, 3.8)
The run was canceled by @Xmader.
build-and-test (ubuntu-22.04, 3.9)
No files were found with the provided path: /cores. No artifacts will be uploaded.
build-and-test (ubuntu-22.04, 3.13)
No files were found with the provided path: /cores. No artifacts will be uploaded.
build-and-test (ubuntu-22.04, 3.10)
No files were found with the provided path: /cores. No artifacts will be uploaded.
build-and-test (ubuntu-22.04, 3.8)
No files were found with the provided path: /cores. No artifacts will be uploaded.
build-and-test (ubuntu-22.04, 3.12)
No files were found with the provided path: /cores. No artifacts will be uploaded.
build-and-test (ubuntu-22.04, 3.11)
No files were found with the provided path: /cores. No artifacts will be uploaded.
build-and-test (macos-13, 3.11)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.11)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.11)
pkgconf 2.4.3 is already installed and up-to-date. To reinstall 2.4.3, run: brew reinstall pkgconf
build-and-test (macos-13, 3.11)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
build-and-test (macos-13, 3.10)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.10)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.10)
pkgconf 2.4.3 is already installed and up-to-date. To reinstall 2.4.3, run: brew reinstall pkgconf
build-and-test (macos-13, 3.10)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
build-and-test (macos-13, 3.9)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.9)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.9)
pkgconf 2.4.3 is already installed and up-to-date. To reinstall 2.4.3, run: brew reinstall pkgconf
build-and-test (macos-13, 3.9)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
build-and-test (macos-13, 3.12)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.12)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.12)
pkgconf 2.4.3 is already installed and up-to-date. To reinstall 2.4.3, run: brew reinstall pkgconf
build-and-test (macos-13, 3.12)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.
build-and-test (macos-13, 3.8)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.8)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.8)
pkgconf 2.4.3 is already installed and up-to-date. To reinstall 2.4.3, run: brew reinstall pkgconf
build-and-test (macos-13, 3.8)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag. To silence this message, use the `--formula` flag.

Artifacts

Produced during runtime
Name Size Digest
wheel-15449784561-c07b4b2d14c3046ea639d79fbd8d53e7c03b270f-sdist Expired
302 KB
sha256:39bfdb8bf1d3d26be2da0776249cc5c1b43c14a362552e80803be2972784a811