[Bug 253946] Cirrus-CI runs encountering disk full failures

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253946

            Bug ID: 253946
           Summary: Cirrus-CI runs encountering disk full failures
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: misc
          Assignee: bugs at FreeBSD.org
          Reporter: emaste at freebsd.org

For some time Cirrus-CI runs of the FreeBSD base system src tree (and forks)
have been failing due to a full disk. These runs use standard FreeBSD GCP
images.

https://cirrus-ci.com/github/freebsd/freebsd-src/

Failure snippet:

--- all_subdir_qlnx ---
ERROR: ctfconvert: qlnxr_cm.o.ctf: Cannot finalize temp file: I/O error: No
space left on device
--- all_subdir_vmm ---
fatal error: error in backend: IO failure on output stream: No space left on
device
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace, preprocessed source, and associated run script.
Stack dump:
0.      Program arguments: /usr/local/llvm11/bin/clang -target
x86_64-unknown-freebsd14.0
--sysroot=/usr/obj/tmp/cirrus-ci-build/amd64.amd64/tmp -B/var/empty -O2 -pipe
-fno-common -DVMM_KEEP_STATS -fno-strict-aliasing -Werror -D_KERNEL
-DKLD_MODULE -DKLD_TIED -nostdinc -I/tmp/cirrus-ci-build/sys/amd64/vmm
-I/tmp/cirrus-ci-build/sys/amd64/vmm/io
-I/tmp/cirrus-ci-build/sys/amd64/vmm/intel
-I/tmp/cirrus-ci-build/sys/amd64/vmm/amd -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/tmp/cirrus-ci-build/amd64.amd64/sys/GENERIC/opt_global.h -I.
-I/tmp/cirrus-ci-build/sys -I/tmp/cirrus-ci-build/sys/contrib/ck/include
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-fdebug-prefix-map=./machine=/tmp/cirrus-ci-build/sys/amd64/include
-fdebug-prefix-map=./x86=/tmp/cirrus-ci-build/sys/x86/include
-I/usr/obj/tmp/cirrus-ci-build/amd64.amd64/sys/GENERIC -MD -MF.depend.vmm.o
-MTvmm.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign
-D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs
-fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare
-Wno-error-empty-body -Wno-error-parentheses-equality
-Wno-error-unused-function -Wno-error-pointer-sign
-Wno-error-shift-negative-value -Wno-address-of-packed-member
-Wno-format-zero-length -mno-aes -mno-avx -std=iso9899:1999 -c
/tmp/cirrus-ci-build/sys/amd64/vmm/vmm.c -o vmm.o 

I'm not sure of the exact bounds but main at
5f1b1f184b7f12330cf4a027e3db7c6700c67640 was green for me and
1bf86687c2eb744497b6d9fd02b80e9821b1f4d6 was red. There does not appear to be
anything particularly interesting in this range, so I suspect that a change in
the GCP image or the installed ports is responsible.

-- 
You are receiving this mail because:
You are the assignee for the bug.