Control: tag -1 moreinfo Hi Simon, thanks for reporting this issue, and sorry for not getting back to you earlier.
Simon Josefsson <si...@josefsson.org> writes: > Hi. I've seen this build failure a couple of times when doing reverse > builds on Salsa, and it seems unrelated to the packages I'm doing > reverse builds of. Have you seen this build error before? Maybe it is > some peculiarity with Salsa CI but would be nice to have fixed anyway. > > https://salsa.debian.org/jas/golang-github-sigstore-sigstore/-/jobs/6912217 > > /Simon > > dh_auto_test -v --max-parallel=2 -- -tags "apparmor seccomp selinux > systemd libsubid cni" > cd _output && go test -vet=off -v -p 2 -tags "apparmor seccomp > selinux systemd libsubid cni" github.com/containers/podman/cmd/podman > github.com/containers/podman/cmd/rootlessport > github.com/containers/podman/cmd/quadlet > === RUN TestFormatError > --- PASS: TestFormatError (0.00s) > === RUN TestFormatOCIError > --- PASS: TestFormatOCIError (0.00s) > === RUN TestShellCompletionFunctions > --- PASS: TestShellCompletionFunctions (0.02s) > PASS > ok github.com/containers/podman/cmd/podman 0.100s > === RUN TestDualStackSplit > --- PASS: TestDualStackSplit (0.00s) > PASS > ok github.com/containers/podman/cmd/rootlessport 0.005s > === RUN TestIsUnambiguousName > --- PASS: TestIsUnambiguousName (0.00s) > === RUN TestUnitDirs > quadlet-generator[31651]: ./relative/path not a valid file path > === RUN TestIsUnambiguousName > --- PASS: TestIsUnambiguousName (0.00s) > === RUN TestUnitDirs > [/proc/self/exe -test.testlogfile=/tmp/go- > build2617256572/b1094/testlog.txt -test.paniconexit0 - > test.timeout=10m0s -test.v=true] > --- PASS: TestUnitDirs (0.00s) > PASS > --- FAIL: TestUnitDirs (0.01s) > panic: runtime error: invalid memory address or nil pointer dereference > [recovered] > panic: runtime error: invalid memory address or nil pointer > dereference > [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x5c8ff5] > goroutine 23 [running]: > testing.tRunner.func1.2({0x5f1840, 0x7bed50}) > /usr/lib/go-1.23/src/testing/testing.go:1632 +0x230 > testing.tRunner.func1() > /usr/lib/go-1.23/src/testing/testing.go:1635 +0x35e > panic({0x5f1840?, 0x7bed50?}) > /usr/lib/go-1.23/src/runtime/panic.go:785 +0x132 > github.com/containers/podman/cmd/quadlet.TestUnitDirs(0xc0000bcb60) > /builds/jas/golang-github-sigstore- > sigstore/debian/output/podman- > 5.3.1+ds1/_output/src/github.com/containers/podman/cmd/quadlet/main_tes > t.go:213 +0x1615 The most recent change to this file was this PR: https://github.com/containers/podman/pull/24974 What version of podman where you seeing this segfault most recently? Do all of the instances include this change or do they not?
