Open liangfok opened 10 months ago
Closing since this is first occurrence.
We had another incidence today -- albeit in a different test.
Three more failures, all in different tests:
3/29 segfault in //multibody/contact_solvers:minimum_degree_ordering_test
in https://drake-jenkins.csail.mit.edu/view/Nightly%20Production/job/linux-jammy-clang-bazel-nightly-coverage/175/
4/1 segfault in //math:hopf_coordinate_test
: linux-jammy-gcc-bazel-nightly-coverage
Reopening the issue per the buildcop playbook. I tried reproducing the segfault locally but wasn't able to do it with a handful of runs.
4/9 //multibody/fem:dirichlet_boundary_condition_test
linux-jammy-clang-bazel-nightly-coverage
4/15: //multibody/parsing:package_map_remote_test
https://drake-jenkins.csail.mit.edu/view/Nightly%20Production/job/linux-jammy-clang-bazel-nightly-coverage/192/
5/21 //common:dummy_value_test failed in linux-jammy-clang-bazel-nightly-coverage
9/19 //common:extract_double_test failed in linux-jammy-clang-bazel-nightly-coverage
9/24 //manipulation/kuka_iiwa:iiwa_status_receiver_test failed in https://drake-jenkins.csail.mit.edu/job/linux-jammy-clang-bazel-nightly-coverage/355/consoleFull
11/19 - linux-jammy-clang-bazel-nightly-coverage failed with a segfault in //systems/primitives:vector_log_test
What happened?
The following failure occured in nightly production:
Links: