Use meson in sage-the-distro #4995
Triggered via pull request
December 10, 2024 00:55
dimpase
Status
Failure
Total duration
1h 40m 52s
Artifacts
–
ci-linux-incremental.yml
on: pull_request
List changed packages
1m 56s
Matrix: constraints_pkgs-norequirements / linux
Matrix: site / linux
Matrix: test / linux
Annotations
38 errors and 20 warnings
|
constraints_pkgs-norequirements / linux (debian-bookworm, standard)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
constraints_pkgs-norequirements / linux (debian-bookworm, standard)
Process completed with exit code 143.
|
|
test / linux (ubuntu-focal, standard)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test / linux (ubuntu-focal, standard)
Process completed with exit code 143.
|
|
constraints_pkgs-norequirements / linux (fedora-40, standard)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
constraints_pkgs-norequirements / linux (fedora-40, standard)
Process completed with exit code 143.
|
|
test / linux (ubuntu-focal, minimal)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test / linux (ubuntu-focal, minimal)
Process completed with exit code 143.
|
|
test / linux (ubuntu-noble, minimal)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test / linux (ubuntu-noble, minimal)
Process completed with exit code 143.
|
|
constraints_pkgs-norequirements / linux (ubuntu-noble, standard)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
constraints_pkgs-norequirements / linux (ubuntu-noble, standard)
Process completed with exit code 143.
|
|
site / linux (fedora-40, standard-sitepackages)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
site / linux (fedora-40, standard-sitepackages)
Process completed with exit code 143.
|
|
site / linux (gentoo-python3.11, standard-sitepackages)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
site / linux (gentoo-python3.11, standard-sitepackages)
Process completed with exit code 143.
|
|
test / linux (fedora-40, standard)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test / linux (fedora-40, standard)
Process completed with exit code 143.
|
|
test / linux (fedora-30, standard)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test / linux (fedora-30, standard)
Process completed with exit code 143.
|
|
constraints_pkgs-norequirements / linux (ubuntu-focal, standard)
The hosted runner: GitHub Actions 11 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.
|
|
constraints_pkgs-norequirements / linux (debian-bullseye-i386, standard)
The hosted runner: GitHub Actions 13 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.
|
|
test / linux (debian-bookworm, minimal)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
test / linux (debian-bookworm, minimal)
The hosted runner: GitHub Actions 22 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.
|
|
test / linux (ubuntu-noble, standard)
The hosted runner: GitHub Actions 33 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.
|
|
test / linux (debian-bullseye, minimal)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
test / linux (debian-bullseye, minimal)
The hosted runner: GitHub Actions 57 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.
|
|
site / linux (archlinux-latest, standard-sitepackages)
The hosted runner: GitHub Actions 55 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.
|
|
test / linux (debian-bullseye, standard)
The hosted runner: GitHub Actions 60 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.
|
|
test / linux (fedora-40, minimal)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test / linux (fedora-40, minimal)
Process completed with exit code 143.
|
|
test / linux (gentoo-python3.11, standard)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test / linux (gentoo-python3.11, standard)
Process completed with exit code 143.
|
|
test / linux (fedora-30, minimal)
The hosted runner: GitHub Actions 23 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.
|
|
test / linux (gentoo-python3.11, minimal)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test / linux (gentoo-python3.11, minimal)
Process completed with exit code 143.
|
|
test / linux (debian-bullseye-i386, standard)
The hosted runner: GitHub Actions 11 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.
|
|
test / linux (debian-bullseye-i386, minimal)
The hosted runner: GitHub Actions 41 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.
|
|
List changed packages
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
List changed packages
fatal: no submodule mapping found in .gitmodules for path 'subprojects/factory'
|
|
List changed packages
Unable to find merge base between f48da11b6dcffbc328d4b0cd2ebc25995c7e86ca and 4ddfb71ee11679de540c00d5269def1a96cc9c9a
|
|
List changed packages
The process '/usr/bin/git' failed with exit code 128
|
|
test / linux (debian-bookworm, standard)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test / linux (debian-bookworm, standard)
Received request to deprovision: The request was cancelled by the remote provider.
|
|
constraints_pkgs-norequirements / linux (ubuntu-focal, standard)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
constraints_pkgs-norequirements / linux (ubuntu-focal, standard)
Received request to deprovision: The request was cancelled by the remote provider.
|
|
constraints_pkgs-norequirements / linux (debian-bullseye-i386, standard)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test / linux (debian-bookworm, minimal)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test / linux (ubuntu-noble, standard)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test / linux (ubuntu-noble, standard)
Received request to deprovision: The request was cancelled by the remote provider.
|
|
test / linux (debian-bullseye, minimal)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
site / linux (archlinux-latest, standard-sitepackages)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
site / linux (archlinux-latest, standard-sitepackages)
Received request to deprovision: The request was cancelled by the remote provider.
|
|
test / linux (debian-bullseye, standard)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test / linux (fedora-30, minimal)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test / linux (fedora-30, minimal)
Received request to deprovision: The request was cancelled by the remote provider.
|
|
test / linux (debian-bullseye-i386, standard)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test / linux (debian-bullseye-i386, minimal)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|