Open fujitatomoya opened 5 months ago
CC: @clalancette @sloretz
@rafa-martin thanks for checking.
@clalancette @sloretz @ahcorde can either of you have a look?
@ros-pull-request-builder retest this please
@clalancette @sloretz @ahcorde Friendly ping for review
@fujitatomoya There are some test failures in the RPR job and they are repeating after RPR job re-run. Also the previous Linux CI job was also failing. Need to either restart it or address failures. Could you please take a look at it?
all tests seem to be passed, but no result available error with rpr job. (https://build.ros2.org/job/Rpr__ros2cli__ubuntu_noble_amd64/24/testReport/(root)/ros2cli/pytest_missing_result/)
i will rebase and restart the CI again.
@fujitatomoya As regards:
all tests seem to be passed, but no result available error with rpr job. (https://build.ros2.org/job/Rpr__ros2cli__ubuntu_noble_amd64/24/testReport/(root)/ros2cli/pytest_missing_result/)
i will rebase and restart the CI again.
From the raw log section
Summary: 15 packages finished [20min 27s] 13 packages had stderr output: ros2action ros2cli ros2component ros2doctor ros2interface ros2lifecycle ros2multicast ros2node ros2param ros2pkg ros2run ros2service ros2topic 1 package had test failures: ros2cli
It was a segfault in python code and test timed out. A bit of details about failure from the same log:
RHEL
failure is missing result, that i am not sure what went wrong. I will retry RHEL
CI.
about rpr job failure, that is segmentation fault during garbage-collecting, stack trace does not even include our fix...
@ros-pull-request-builder retest this please
address https://github.com/ros2/ros2cli/issues/895