Skip to content
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

test_echo_pub.TestROS2TopicEchoPub.test_pub_maxwait_yields failed often recently #809

Closed
iuhilnehc-ynos opened this issue Mar 2, 2023 · 5 comments · Fixed by #810
Closed

Comments

@iuhilnehc-ynos
Copy link

Bug report

log on CI for Linux

Error Message
test_echo_pub.TestROS2TopicEchoPub.test_pub_maxwait_yields failed
Stacktrace
======================================================================================================================================================
FAIL: test_echo_pub.TestROS2TopicEchoPub.test_pub_maxwait_yields
------------------------------------------------------------------------------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jenkins-agent/workspace/ci_linux/ws/install/launch_testing/lib/python3.10/site-packages/launch_testing/markers.py", line 57, in _wrapper
    return func(self, *args, **kwargs)
  File "/home/jenkins-agent/workspace/ci_linux/ws/src/ros2/ros2cli/ros2topic/test/test_echo_pub.py", line 258, in test_pub_maxwait_yields
    assert future.done()
AssertionError: assert False
 +  where False = <bound method Future.done of <rclpy.task.Future object at 0x7f1dd13c2500>>()
 +    where <bound method Future.done of <rclpy.task.Future object at 0x7f1dd13c2500>> = <rclpy.task.Future object at 0x7f1dd13c2500>.done

https://ci.ros2.org/job/ci_linux/18139/testReport/junit/ros2topic.ros2topic.test/test_echo_pub/test_echo_pub/
https://ci.ros2.org/job/ci_linux/18137/testReport/junit/ros2topic.ros2topic.test/test_echo_pub/test_echo_pub/
https://ci.ros2.org/job/ci_linux/18133/testReport/junit/ros2topic.ros2topic.test/test_echo_pub/test_echo_pub/
https://ci.ros2.org/job/ci_linux/18129/testReport/ros2topic.ros2topic.test/test_echo_pub/test_echo_pub/
https://ci.ros2.org/job/ci_linux/18128/testReport/junit/ros2topic.ros2topic.test/test_echo_pub/test_echo_pub/
https://ci.ros2.org/job/ci_linux/18126/testReport/junit/ros2topic.ros2topic.test/test_echo_pub/test_echo_pub/

@fujitatomoya
Copy link
Collaborator

@iuhilnehc-ynos this is happening because of #800?

@iuhilnehc-ynos
Copy link
Author

I think so, but I haven't dived into the deep.

@fujitatomoya
Copy link
Collaborator

@Crola1702 @Blast545 CCed.

@iuhilnehc-ynos
Copy link
Author

iuhilnehc-ynos commented Mar 2, 2023

The message can't be reliable to receive without a correct QoS setting if a message is only published once (-t 1).
I am going to change the -t 1 with -t 10.

@Crola1702
Copy link
Contributor

FYI: @arjo129

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants