On 25/11/2024 12:17 pm, Jan Beulich wrote: > On 25.11.2024 13:14, GitLab wrote: >> >> Pipeline #1558962580 has failed! >> >> Project: xen ( https://gitlab.com/xen-project/hardware/xen ) >> Branch: staging ( >> https://gitlab.com/xen-project/hardware/xen/-/commits/staging ) >> >> Commit: 2e853c19 ( >> https://gitlab.com/xen-project/hardware/xen/-/commit/2e853c19204e2d660a8becf4b377cc99216854dd >> ) >> Commit Message: xen/common: Move gic_dt_preinit() to common cod... >> Commit Author: Oleksii Kurochko ( https://gitlab.com/olkur ) >> Committed by: Jan Beulich ( https://gitlab.com/jbeulich ) >> >> >> Pipeline #1558962580 ( >> https://gitlab.com/xen-project/hardware/xen/-/pipelines/1558962580 ) >> triggered by Jan Beulich ( https://gitlab.com/jbeulich ) >> had 1 failed job. >> >> Job #8461870351 ( >> https://gitlab.com/xen-project/hardware/xen/-/jobs/8461870351/raw ) >> >> Stage: build >> Name: debian-11-riscv64-gcc > ERROR: Job failed: failed to pull image > "registry.gitlab.com/xen-project/xen/debian:11-riscv64" with specified > policies [always]: Error response from daemon: Get > "https://registry.gitlab.com/v2/": dial tcp: lookup registry.gitlab.com on > 127.0.0.53:53: read udp 127.0.0.1:53667->127.0.0.53:53: read: connection > refused (manager.go:251:0s) > > i.e. nothing on the side of what's under test. I'm afraid I don't even know > what to do in such a case, to get things moving again.
It seems Gitlab is having networking problems. Hit the retry button. (top right hand side, 2 arrows in a circle, white on blue background). I've rerun this test for now, but I expect others will fail. ~Andrew
