Closed iuhilnehc-ynos closed 1 year ago
ran CI with wrong value --package-select
for CI_TEST_ARGS before, which should be --packages-select
.
rerun CI (2/10),
22:29:56 launch_testing_examples\check_multiple_nodes_launch_test.py . [ 22%]
no more `re-test` action
rerun CI (3/10),
rerun CI (4/10),
rerun CI (5/10),
rerun CI (6/10),
In order to not occupy the CI resource, I'll rerun a full CI later.
I'm going to go ahead and merge this one, since it is low-risk and seems to be helping. We can always do another follow-up if this isn't enough.
A flaky test about
launch_testing_examples\check_multiple_nodes_launch_test.py
is always reported while running CI.After comparing the success and failure cases between https://ci.ros2.org/job/ci_windows/18721/consoleFull and https://ci.ros2.org/job/ci_windows/18738/consoleFull, I suspect that the timeout of waiting on the Window platform might not be enough.
Successful log in https://ci.ros2.org/job/ci_windows/18721/consoleFull,
Failure log in https://ci.ros2.org/job/ci_windows/18738/consoleFull.
We can find two
re-test
actions even in the successful log. (RR.)