-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Biannual linux kernel/security update for CI image #21668
Comments
All Jammy and Noble images have been updated. Both provisioned images were also updated and re-provisioned. |
Reopening this as something went wrong with the Jammy update, see https://drakedevelopers.slack.com/archives/C270MN28G/p1720809110296759 |
An example of the failure with the initial update is (from https://drake-jenkins.csail.mit.edu/view/Pull%20Request/job/linux-jammy-clang-bazel-experimental-leak-sanitizer/4202/consoleFull)
|
I tried the update again, spun up an instance from the updated image, ran the tests and saw the same results. Note this error only appears after updating the kernel. Updating the unprovisioned image (apt update and upgrade, ignoring the held back On my local machine, I also get the error when running: @jwnimmer-tri when you have a chance, can you see if the above command succeeds for you locally? |
Locally, I'm currently using this kernel:
Running Drilling down and running I'll see if I can figure out where things go wrong. |
I wasn't able to get any traction. The corefiles don't work, and LSan programs apparently can't be run under gdb. Even the segfault doesn't appear to have any details that I can google around for. I think you might have to set up an experiment somewhere where you bisect through different kernel versions, and see if that sheds any light. |
Interesting... I will try to narrow down which version it started failing. |
Previous issue: #18617
The text was updated successfully, but these errors were encountered: