-
Notifications
You must be signed in to change notification settings - Fork 277
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
π¨βπΎ Add a potential temporary fix for flaky tests on macOS #807
Conversation
Do you think we could get a similar effect by including them into the test executable? That would solve the test's issue while leaving the core library intact. I can't see the results from CI, and it looks like 3 tests failed on Homebrew. I'll sync this with |
I think some, if not all, of the remaining failures might be fixed by gazebosim/gz-common#227. |
So you think they're not related to how the components are registered, as explained on #806? One thing all these test failures have in common is a segfault at startup, even before any console messages are printed. |
Codecov Report
@@ Coverage Diff @@
## ign-gazebo5 #807 +/- ##
===============================================
- Coverage 67.04% 66.95% -0.10%
===============================================
Files 276 276
Lines 21049 21023 -26
===============================================
- Hits 14112 14075 -37
- Misses 6937 6948 +11
Continue to review full report at Codecov.
|
FWIW, there were no homebrew failures in the latest run π¬ |
I've disabled multi-threading in 6ac5110. Let's what this does. |
It's tough to tell from just one CI run because these failures are very flaky. It would be nice to be able to set something like colcon's |
we currently have a script for running
we could add something similar for |
Yeah, |
+1
I believe it is, but it's flaky and I haven't seen it in a while. |
https://build.osrfoundation.org/job/ignition_gazebo-ci-pr_any-homebrew-amd64/5997/ ran each test until it failed with a maximum of 100 runs each. The logs show:
I suspect the failure in For comparision, I'll run |
In the interest of time, I only did The logs show:
I'm guessing |
So we're testing 2 different things at once here. The header includes and the worker threads. I think we should examine them separately. If it turns out the worker threads are the problem, I believe the next step could be to disable multi-threading just for macOS until we have time to try and address the underlying issue. I'm assuming no one has time to debug these failures on a mac right now. I think it's worth sacrificing performance for reliability for now (for Mac users and CI). |
Now that ign-common 4.5 has been released, we've have had much better homebrew CI https://build.osrfoundation.org/job/ignition_gazebo-ci-ign-gazebo5-homebrew-amd64/ (starting from build 53).
I have attached the test result csv file for posterity: Test Results.csv |
Signed-off-by: Addisu Z. Taddese <[email protected]>
Signed-off-by: Addisu Z. Taddese <[email protected]>
75172ca
to
6cb1354
Compare
@azeey , Edifice will EOL next week. Do you want to retarget this to |
Yup. Will do. |
Closing in favor of #1836 |
π¦ Bug fix
Relates to #806
Summary
A potential solution to the problem of flaky tests on macOS is to include all known components in libignition-gazebo.so. I have tested this locally with Address Sanitizer and it seems to work.
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge