Carl Mueller-Roemer

@Hi-Angel I like the much cleaner interface, however with the rust tool (v0.3.0 installed using cargo install flamegraph) I get the exact same "function

This is a serious problem. We can basically not trust out Jenkins pipeline because of this. Is there a way to at least systematically obtain the error code if a...

catkin_test_results says "Summary: 0 tests, 0 errors, 0 failures, 0 skipped", so one would need to diff the number of tests here with the number of tests found, which seems...

For anybody else who's unhappy with this, gtest creates: MISSING-gtest-*.xml test reports This way you can temporarily work around this deficiency.

I've been trying to implement the workaround. However trying to do `echo > /proc//fd/6` or `echo -n +++ > /proc//fd/6` doesn't seem to work. It tells me that the device...

I added some warnings (making the output more verbose), which consistently triggers this behavior. Just wanted to confirm that it's probaly related to the amount of output.

The workaround still doesn't get this unstuck, however now it didn't tell me the device didn't exist, and I checked, I can see writing to stdout and stderr (/proc/$(pgrep -x...

Debugging into catkin I find whenever you stop the debugger it has the same callstack: ``` MainThread: _decode / io.py on_stderr_received / io.py run_until_complete / executor.py build_isolated_workspace / build.py main...

When it hangs there are about ~4000 chars in stderr always (never ending, but not constant). When it doesn't hang there are up to about ~2500 chars arriving, normally ~200...

@abrandemuehl @k-okada May I suggest debugging catkin_tools and checking how much output is read from stderr? Maybe it's the same problem if this message generation is very wordy.