-
Couldn't load subscription status.
- Fork 300
Fix flaky controller switch test #1447
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
Fix flaky controller switch test #1447
Conversation
We were starting the tests right after we started the driver. However, the test requires that all controllers are actually available. This commit adds a check whether all required controller are actually loaded. If not all required controllers are found in a specific time, the test will throw an exception and therefore fail.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1447 +/- ##
========================================
+ Coverage 3.59% 5.11% +1.52%
========================================
Files 13 33 +20
Lines 947 3404 +2457
Branches 152 427 +275
========================================
+ Hits 34 174 +140
- Misses 843 3228 +2385
+ Partials 70 2 -68
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
We were starting the tests right after we started the driver. However, the test requires that all controllers are actually available. This commit adds a check whether all required controllers are actually loaded. If not all required controllers are found in a specific time, the test will throw an exception and therefore fail. (cherry picked from commit d675a36)
We were starting the tests right after we started the driver. However, the test requires that all controllers are actually available. This commit adds a check whether all required controllers are actually loaded. If not all required controllers are found in a specific time, the test will throw an exception and therefore fail. (cherry picked from commit d675a36)
We were starting the tests right after we started the driver. However, the test requires that all controllers are actually available. This commit adds a check whether all required controllers are actually loaded. If not all required controllers are found in a specific time, the test will throw an exception and therefore fail.
We were starting the tests right after we started the driver. However, the test requires that all controllers are actually available. This commit adds a check whether all required controllers are actually loaded. If not all required controllers are found in a specific time, the test will throw an exception and therefore fail.
We were starting the tests right after we started the driver. However, the test requires that all controllers are actually available. This commit adds a check whether all required controller are actually loaded.
If not all required controllers are found in a specific time, the test will throw an exception and therefore fail.
This should fix failures such as https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/actions/runs/16107576360/job/45452852404