-
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
Unknown non-recurrent failures in //bindings/pydrake/systems:py/general_test #19335
Comments
|
Happened again. Also monterey. Reopening -- there's something in the monterey toolchain that's tickling pybind object identity semantics. |
@jwnimmer-tri speculates that this may share a common source with #19394 https://drakedevelopers.slack.com/archives/C270MN28G/p1683817207919069?thread_ts=1683810179.404429&cid=C270MN28G |
It happened again last night (5/16/23) in mac-arm-monterey-clang-bazel-nightly-debug/196. |
Again on 05/24/23: mac-x86-monterey-unprovisioned-clang-bazel-nightly-release/201/ |
Another instance on 5/24: https://drake-jenkins.csail.mit.edu/job/mac-arm-monterey-clang-bazel-continuous-release/762/ |
|
The test has a runtime of like 2 seconds. We should mark it |
Another instance, this time on sonoma https://drake-jenkins.csail.mit.edu/view/Nightly%20Production/job/mac-arm-sonoma-unprovisioned-clang-bazel-nightly-release/112/ |
First occurrence came up in continuous macOS x86:
We booted a CI machine to try and triage thinking it was related to the workspace upgrades (#19332), however it is not. It also appears under df13567 but CI does not always pick it up. May not be limited to macOS.
Testing can sometimes reproduce it if you run it multiple times. In the macOS case, the command line:
$ bazel test --cache_test_results=no --runs_per_test=150 --config=clang --compilation_mode=opt --test_timeout=300,1500,4500,-1 //bindings/pydrake/systems:py/general_test
For now we label this "buildcop noise" and will log future occurrences, while silently ignoring it otherwise.
The text was updated successfully, but these errors were encountered: