-
Notifications
You must be signed in to change notification settings - Fork 293
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
Stop server to reduce flakiness of UNIT_Server_TEST #2740
base: gz-sim9
Are you sure you want to change the base?
Conversation
Signed-off-by: Steve Peters <[email protected]>
Passing test console output (from macOS)
|
Failing test console output
|
looks like a race condition. If the systems' PostUpdate thread started running, the test gets stuck shutting down. Maybe one thing to try is not load the scene_broadcaster system as it does not look like it's needed for this test (and probably need to change the expectation of system count to |
It would be nice if we could could fix the race condition though. |
Signed-off-by: Steve Peters <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## gz-sim9 #2740 +/- ##
==========================================
Coverage ? 68.94%
==========================================
Files ? 345
Lines ? 33349
Branches ? 0
==========================================
Hits ? 22994
Misses ? 10355
Partials ? 0 ☔ View full report in Codecov by Sentry. |
Running test with thread sanitizer, like According to my observations, threads are stuck on a barrier, while rest of the code are starting destroying in the end of test and eventually it stuck in destructor, on thread join operation.
Line number may be skewed(this log is a couple weeks old), but it's inside Still this bug has not the best reproducibility, sometimes executable should be restarted more than 100 times to reproduce hang |
EXPECT_TRUE(executed); | ||
EXPECT_TRUE(result); | ||
EXPECT_EQ("TestSensorSystem", rep.data()); | ||
server.Stop(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess ~ServerPrivate
is already calling Stop()
I'm not sure if this actually fixes anything
🦟 Bug fix
Fixes #2609.
Summary
The
ServerRepeat/ServerFixture.ServerConfigSensorPlugin/0
test was timing out flakily. This adds print statements and aserver->Stop();
call to aid in shutdown.Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.