Skip to content

Dockerfile: update Renode to 1.15.2 #287

Dockerfile: update Renode to 1.15.2

Dockerfile: update Renode to 1.15.2 #287

Triggered via pull request August 19, 2024 08:35
Status Failure
Total duration 10m 43s
Artifacts

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
Build (linux/arm64)
Error: buildah exited with code 1 Resolved "ubuntu" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf) Trying to pull docker.io/library/ubuntu:22.04... Getting image source signatures Copying blob sha256:e63ce922f0229bde5aea9f366c46883dcd23747e7d2c541f16665f199dbf98b8 Copying config sha256:7f965f3f8aaea925b99655563057f7177eff9d8828c27ee0d89872d84716a219 Writing manifest to image destination debconf: delaying package configuration, since apt-utils is not installed 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 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. 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. 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. subprocess exited with status 1 subprocess exited with status 1 Error: building at STEP "RUN python3 -m pip install -U --no-cache-dir pip && pip3 install -U --no-cache-dir wheel setuptools && pip3 install --no-cache-dir pygobject && pip3 install --no-cache-dir -r https://raw.githubusercontent.com/zephyrproject-rtos/zephyr/main/scripts/requirements.txt -r https://raw.githubusercontent.com/zephyrproject-rtos/mcuboot/main/scripts/requirements.txt GitPython imgtool junitparser junit2html numpy protobuf PyGithub pylint sh statistics west nrf-regtool>=5.3.0 && pip3 check": exit status 1
Build (linux/arm64)
Error: failed to run script step: command terminated with non-zero exit code: Error executing in Docker Container: 1
Build (linux/arm64)
Process completed with exit code 1.
Build (linux/arm64)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
Build (linux/amd64)
The job was canceled because "linux_arm64_arm64_zephyr-" failed.
Build (linux/amd64)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
Build (linux/arm64)
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.317.0. Please update to the latest version 2.319.1