Revert "Skip CLI tests on Windows until we resolve the blocking/hanging isuse. (#489)"#583
Revert "Skip CLI tests on Windows until we resolve the blocking/hanging isuse. (#489)"#583
Conversation
2f819bc to
4018dec
Compare
|
Rebased to solve failing DCO check. |
ivanpauno
left a comment
There was a problem hiding this comment.
LGTM with green CI!
It's worth notifying everybody about these tests being reactivated, just in case they start hanging again.
|
Once/if Windows CI passes, I'll release |
|
Hmm, tests don't hang anymore but they are as flaky as possible. I have to circle back. |
|
Oh, I missed those. Thanks @ivanpauno ! I'm still fighting tests to pass on Windows though. |
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
a0e87ed to
c0d8da2
Compare
|
Hmm, some failing As side note, I am a bit worried about the long timeouts. |
Yeah, that's a problem. It's not useful for users, and the other problem is that adding these test look like they will add ~1 hour to our (already very long) CI times. osrf/osrf_pycommon#66 will help somewhat . Other than that, we'd need to go in and do an analysis of what is taking so long. |
|
I'm proactively putting this in the Galactic backlog. Ideally, I think we should figure out why these CLIs are so slow on Windows before Galactic is out, but I don't know if that's realistic. |
|
One thing I've noticed while doing manual source testing on Windows. CLIs are slow to respond when the daemon is up. |
|
The issue with CLI daemons in Windows is tracked by #637. |
Hopefully ros2/launch#476 fixed this 🤞
CI up to
ros2topic,ros2action,ros2interface,ros2lifecycle,ros2node,ros2pkg, andros2service(repeated 5 times):