@rpoyner-tri explained that the kcov in CI might take a long time to create coverage reports due to randomly slow filesystems.
I re-ran the test on my Jammy with this command:
bazel run --config=gcc --compilation_mode=dbg --config=kcov //geometry/optimization:iris_internal_test
and it passed in 7 minutes.
Version
68a11682c9f4768c16311c1165e339310d412a48
What operating system are you using?
Ubuntu 22.04
What installation option are you using?
compiled from source code using Bazel
Relevant log output
TIMEOUT
-- Test timed out at 2024-10-29 11:54:05 UTC --
//geometry/optimization:iris_internal_test TIMEOUT in 600.3s
/media/ephemeral0/ubuntu/workspace/linux-jammy-gcc-bazel-nightly-coverage/_bazel_ubuntu/13ab93db129735c0cc7824860397095a/execroot/drake/bazel-out/k8-dbg/testlogs/geometry/optimization/iris_internal_test/test.log
What happened?
Nighly CI has timeout on a coverage test of //geometry/optimization:iris_internal_test in https://drake-jenkins.csail.mit.edu/job/linux-jammy-gcc-bazel-nightly-coverage/392/
@rpoyner-tri explained that the kcov in CI might take a long time to create coverage reports due to randomly slow filesystems.
I re-ran the test on my Jammy with this command:
and it passed in 7 minutes.
Version
68a11682c9f4768c16311c1165e339310d412a48
What operating system are you using?
Ubuntu 22.04
What installation option are you using?
compiled from source code using Bazel
Relevant log output