On 11/03/2024 10:15 am, Jan Beulich wrote: > On 11.03.2024 11:00, GitLab wrote: >> >> Pipeline #1208433952 has failed! >> >> Project: xen ( https://gitlab.com/xen-project/hardware/xen ) >> Branch: staging ( >> https://gitlab.com/xen-project/hardware/xen/-/commits/staging ) >> >> Commit: e90089db ( >> https://gitlab.com/xen-project/hardware/xen/-/commit/e90089db3fab06dc8947fcd64f1ed54569e708a6 >> ) >> Commit Message: arm/smmu: address some violations of MISRA C Ru... >> Commit Author: Nicola Vetrini >> Committed by: Jan Beulich ( https://gitlab.com/jbeulich ) >> >> >> Pipeline #1208433952 ( >> https://gitlab.com/xen-project/hardware/xen/-/pipelines/1208433952 ) >> triggered by Jan Beulich ( https://gitlab.com/jbeulich ) >> had 2 failed jobs. >> >> Job #6362049499 ( >> https://gitlab.com/xen-project/hardware/xen/-/jobs/6362049499/raw ) >> >> Stage: build >> Name: ubuntu-trusty-gcc > I'm afraid I can't make sense of this supposed failure.
fatal: unable to access 'https://gitlab.com/xen-project/hardware/xen.git/': Couldn't connect to server Networking failure. > >> Job #6362049553 ( >> https://gitlab.com/xen-project/hardware/xen/-/jobs/6362049553/raw ) >> >> Stage: test >> Name: build-each-commit-gcc > This one simply timed out once again, for it taking too long to build a > dozen commits in non-incremental fashion. Irritatingly the timeout is per-repo not a global setting. I've bumped this back up to 3h to match the other main repos. ~Andrew
