-
Notifications
You must be signed in to change notification settings - Fork 53
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
New DDS profile for a flaky test #437
base: main
Are you sure you want to change the base?
Conversation
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.
LGTM as long as CI passes
@@ -130,6 +130,8 @@ target_include_directories(test_kinematic_service | |||
) | |||
target_link_libraries(test_kinematic_service spot_api) | |||
|
|||
ament_add_pytest_test(spot_driver_pytest ${CMAKE_CURRENT_SOURCE_DIR} TIMEOUT 900) |
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.
Do we want to go with this approach of 900s for all of the tests or the one below which loops over and gives individual tests targets?
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.
To be clear I am not leaning one way or the other. Just checking
Pull Request Test Coverage Report for Build 10117260442Details
💛 - Coveralls |
Change Overview
Added in a new DDS profile based off of https://github.com/bdaiinstitute/bdai/pull/6448 to fix a flaky test caused by race conditions in service discovery in FastDDS.
Testing Done
[x] I ran the pytests locally a few times and saw the flaky test pass but unsure how to robustly test it since it usually passes in CI but not always
Please create a checklist of tests you plan to do and check off the ones that have been completed successfully. Ensure that ROS 2 tests use
domain_coordinator
to prevent port conflicts. Further guidance for testing can be found on the ros utilities wiki.