Michel Hidalgo
Michel Hidalgo
Rebased to solve failing DCO check.
Another round of CI up to `ros2topic`, `ros2action`, `ros2interface`, `ros2lifecycle`, `ros2node`, `ros2pkg`, and `ros2service` (repeated up to 5 times until failure): * Linux [](http://ci.ros2.org/job/ci_linux/13414/) * Linux-aarch64 [](http://ci.ros2.org/job/ci_linux-aarch64/8334/) *...
Once/if Windows CI passes, I'll release `launch` into Rolling to get that Rpr job passing.
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.
Alright, with last commits I can no longer reproduce flaky tests on Windows. Spinning up CI up to `ros2topic`, `ros2action`, `ros2interface`, `ros2lifecycle`, `ros2node`, `ros2pkg`, and `ros2service` (repeated up to 5...
Hmm, some failing `ros2node` tests need an increase in their timeouts, but `ros2topic` test failures are perplexing. I cannot reproduce them in a Windows VM. --- As side note, I...
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...
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 https://github.com/ros2/ros2cli/issues/637.