On 18.10.2023 00:32, GitLab wrote: > > > Pipeline #1040204203 has failed! > > Project: xen ( https://gitlab.com/xen-project/xen ) > Branch: staging ( https://gitlab.com/xen-project/xen/-/commits/staging ) > > Commit: f51c9238 ( > https://gitlab.com/xen-project/xen/-/commit/f51c92383b8dc76233481e2814aa2e905fb9b501 > ) > Commit Message: xen/arm: Check return code from recursive calls... > Commit Author: Michal Orzel ( https://gitlab.com/orzelmichal ) > Committed by: Stefano Stabellini > > > Pipeline #1040204203 ( > https://gitlab.com/xen-project/xen/-/pipelines/1040204203 ) triggered by > Ganis ( https://gitlab.com/ganis ) > had 16 failed jobs. > > Job #5314335376 ( https://gitlab.com/xen-project/xen/-/jobs/5314335376/raw ) > > Stage: build > Name: alpine-3.18-clang > Job #5314335405 ( https://gitlab.com/xen-project/xen/-/jobs/5314335405/raw ) > > Stage: build > Name: debian-bookworm-clang > Job #5314335460 ( https://gitlab.com/xen-project/xen/-/jobs/5314335460/raw ) > > Stage: build > Name: ubuntu-focal-gcc-debug > Job #5314335478 ( https://gitlab.com/xen-project/xen/-/jobs/5314335478/raw ) > > Stage: build > Name: opensuse-tumbleweed-clang-debug > Job #5314335485 ( https://gitlab.com/xen-project/xen/-/jobs/5314335485/raw ) > > Stage: build > Name: opensuse-tumbleweed-gcc-debug > Job #5314335481 ( https://gitlab.com/xen-project/xen/-/jobs/5314335481/raw ) > > Stage: build > Name: opensuse-tumbleweed-gcc > Job #5314335458 ( https://gitlab.com/xen-project/xen/-/jobs/5314335458/raw ) > > Stage: build > Name: ubuntu-focal-gcc > Job #5314335431 ( https://gitlab.com/xen-project/xen/-/jobs/5314335431/raw ) > > Stage: build > Name: fedora-gcc
Picking this as example: ../qemu-xen-dir-remote/io/channel-tls.c:510:1: fatal error: error writing to /tmp/cce3v8eA.s: No space left on device I'm afraid I have to ask to delay plans to further switch processes to go through gitlab until basic problems like (apparently) regular cleanup to provision enough disk space haven't been sorted. Furthermore I'd also like to ask that getting these reports sent to xen-devel@ should be a prereq to further leveraging gitlab. Them being sent to committers@ instead was meant to be a temporary measure only. As an unrelated question: Do we have any control over the formatting of these reporting mails? The grouping of items (i.e. the placement of the apparently but not really separating blank lines) has been broken forever, resulting in at least me always needing to think twice which link belongs to which job. Jan > Job #5314335242 ( https://gitlab.com/xen-project/xen/-/jobs/5314335242/raw ) > > Stage: analyze > Name: eclair-ARM64 > Job #5314335390 ( https://gitlab.com/xen-project/xen/-/jobs/5314335390/raw ) > > Stage: build > Name: debian-stretch-gcc > Job #5314335391 ( https://gitlab.com/xen-project/xen/-/jobs/5314335391/raw ) > > Stage: build > Name: debian-stretch-clang > Job #5314335454 ( https://gitlab.com/xen-project/xen/-/jobs/5314335454/raw ) > > Stage: build > Name: ubuntu-bionic-gcc > Job #5314335461 ( https://gitlab.com/xen-project/xen/-/jobs/5314335461/raw ) > > Stage: build > Name: ubuntu-focal-clang > Job #5314335470 ( https://gitlab.com/xen-project/xen/-/jobs/5314335470/raw ) > > Stage: build > Name: opensuse-leap-gcc > Job #5314335506 ( https://gitlab.com/xen-project/xen/-/jobs/5314335506/raw ) > > Stage: test > Name: adl-pci-pv-x86-64-gcc-debug > Job #5314335466 ( https://gitlab.com/xen-project/xen/-/jobs/5314335466/raw ) > > Stage: build > Name: opensuse-leap-clang >
