You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For build farms which do not manually read in the xunit files, one command which indicates whether or not any tests failed would be nice.
caktin_test_results /path/to/test_results summarizes the tests, but always returns 0, maybe it could have options like --error-code-on-errors and --error-code-on-failures.
For not this works:
python -c "from catkin.test_results import test_results;import sys;sys.exit(sum([v[1] + v[2] for k, v in test_results('build/test_results').iteritems()]))"
The text was updated successfully, but these errors were encountered:
This was implicitly set on <= Ubuntu 16.04 when find_package()-ing
GMock in google_enable_testing(). On 17.04, this doesn't happen, and
Catkin builds a shared library by default. cartographer_ros currently
can't be built as a shared library due to a linking problem (which is
a separate issue - ros#392). This makes building on 17.04 consistent with
older versions of Ubuntu.
For build farms which do not manually read in the xunit files, one command which indicates whether or not any tests failed would be nice.
caktin_test_results /path/to/test_results
summarizes the tests, but always returns 0, maybe it could have options like--error-code-on-errors
and--error-code-on-failures
.For not this works:
python -c "from catkin.test_results import test_results;import sys;sys.exit(sum([v[1] + v[2] for k, v in test_results('build/test_results').iteritems()]))"
The text was updated successfully, but these errors were encountered: