Control: Severity -1 important
Control: Retitle -1 testsuite is flaky

Looking at the build failures, there appears to be at least two tests that
are flaky.

One being in daemon/logger:
https://sources.debian.org/src/docker.io/20.10.25%2Bdfsg1-3/engine/daemon/logger/copier_test.go/#L261-L265

The other one manifesting as a segfault:

=== FAIL: daemon TestExecSetPlatformOpt (0.00s)
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=0x0 pc=0x2424ce6]

goroutine 101 [running]:
testing.tRunner.func1.2({0x26d8820, 0x4032710})
        /usr/lib/go-1.22/src/testing/testing.go:1631 +0x24a
testing.tRunner.func1()
        /usr/lib/go-1.22/src/testing/testing.go:1634 +0x377
panic({0x26d8820?, 0x4032710?})
        /usr/lib/go-1.22/src/runtime/panic.go:770
+0x132github.com/docker/docker/daemon.(*Daemon).execSetPlatformOpt.WithRlimits.func1({0x30820c0?,
0x413aba0?}, {0x0?, 0x0?}, 0x0?, 0xc000a49810)
        
/<<PKGBUILDDIR>>/_build/src/github.com/docker/docker/daemon/oci_linux.go:46
+0x46github.com/docker/docker/daemon.(*Daemon).execSetPlatformOpt(0xc000aa1d88,
0xc000aa1b40, 0xc000aa1998?, 0xc000aa1970)
        
/<<PKGBUILDDIR>>/_build/src/github.com/docker/docker/daemon/exec_linux.go:54
+0x503github.com/docker/docker/daemon.TestExecSetPlatformOpt(0xc000a77a00)
        
/<<PKGBUILDDIR>>/_build/src/github.com/docker/docker/daemon/exec_linux_test.go:26
+0x155
testing.tRunner(0xc000a77a00, 0x2aaeba0)
        /usr/lib/go-1.22/src/testing/testing.go:1689 +0xfb
created by testing.(*T).Run in goroutine 1
        /usr/lib/go-1.22/src/testing/testing.go:1742 +0x390


Source code here:
https://sources.debian.org/src/docker.io/20.10.25%2Bdfsg1-3/engine/daemon/oci_linux.go/#L46


not sure what makes them trigger.  Maybe machines got faster and it is
easier to trigger these issues? Not sure how to go about this, besides
removing the two tests in question.


-- 
regards,
    Reinhard

Reply via email to