-
Notifications
You must be signed in to change notification settings - Fork 129
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
configurable run test verbosity #267
configurable run test verbosity #267
Conversation
b5e0852
to
cbd7143
Compare
this feature reduces our log length from >10000 lines down to 2500! |
@@ -25,11 +25,18 @@ | |||
ici_require_run_in_docker # this script must be run in docker | |||
|
|||
#Define some verbose env vars | |||
#verbose build tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's just "verbose build", not just tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Just some minor glitch, the rest LGTM |
cbd7143
to
8d0f665
Compare
@@ -187,7 +194,7 @@ if [ "$NOT_TEST_BUILD" != "true" ]; then | |||
|
|||
ici_time_start catkin_run_tests | |||
if [ "$BUILDER" == catkin ]; then | |||
catkin run_tests --no-deps --no-status $PKGS_DOWNSTREAM $CATKIN_PARALLEL_TEST_JOBS --make-args $ROS_PARALLEL_TEST_JOBS -- | |||
catkin build --no-deps --catkin-make-args run_tests -- $OPT_RUN_VI --no-status $PKGS_DOWNSTREAM $CATKIN_PARALLEL_TEST_JOBS --make-args $ROS_PARALLEL_TEST_JOBS -- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should I add --summarize
here too - for the sake of consistency with the other build
steps?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure, if it add something interesting.
You can just have a look and decide yourself.
Just had a look at this https://travis-ci.org/ros-industrial/industrial_ci/jobs/330252621 I think |
OPT_RUN_V="-v" | ||
else | ||
OPT_RUN_V="" | ||
fi | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if [ "$VERBOSE_TESTS" = false ]; then
OPT_RUN_V=""
else
OPT_RUN_V="-v"
fi
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😉 I thought it'd be more complicated ^^
(but I'll wait until the decision with/without interleave
is made)
Yes, his was the default before and definately makes sense für the tests. |
@ipa-mdl @130s |
I am happy :) @130s: Should tests be verbose by default or not? |
06b529f
to
75e37f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the iteration. +1 for merge once Travis passes.
follow-up of #255 (comment)
@ipa-mdl
I'm not sure how the environment variable handling works in industrial_ci
also, I was not sure whether/how to set
VERBOSE_TESTS
totrue
by defaultplease guide me here - or take over the branch 😉