Open davepacheco opened 1 year ago
I have the whole test temporary directory, which includes that bunyan log file, CockroachDB stdout/stderr, and the CockroachDB data directory (which includes its logs). I don't have a core file, unfortunately.
dap@catacomb /data/staff/core/issues/omicron-2043 $ ls -l
total 1650
-rw-rw-r--+ 1 dap staff 824987 Dec 11 02:31 omicron-2043-tmpdir.tgz
-rw-rw-r--+ 1 dap staff 29565 Dec 11 02:30 run-20013.out
dap@catacomb /data/staff/core/issues/omicron-2043 $
While trying to reproduce the various CockroachDB/Go issues, I've been running the Omicron test suite in a loop, and with a bit of extra instrumentation. I got a new failure mode here:
Usually when this happens, Cockroach bails out before opening its listening socket. This time, it bailed out some time later:
We have to log in the stderr log file to find the problem:
It's interesting that this one does not involve the Go runtime directly.
This is with:
and the test suite run is from 1edc4ab94290e7c1d0596033e69010095be828b2, which is a tiny branch from "main" at commit 6fa27a335a58181262e85824922bdf0dc68cfc9b.
I will put some data into catacomb:/data/staff/core/issues/omicron-$this_ticket.