SZEDER Gábor <szeder....@gmail.com> writes: >> >> +if test true = "$TRAVIS" >> >> +then >> >> +... >> >> + export GIT_PROVE_OPTS="--timer --jobs 3 --state=failed,slow,save" >> >> + export GIT_TEST_OPTS="--verbose-log -x --immediate" >> >> +fi >> > ... > > $GIT_PROVE_OPTS and $GIT_TEST_OPTS, however, are only used in > 't/Makefile' but not in the build scripts, thus their values don't > show up in the build logs. > > I run some Travis CI builds with custom $GIT_TEST_OPTS, which, of > course, conflicted with this patch, and I messed up the conflict > resolution. I think I would have noticed sooner what went wrong, if > the value of $GIT_TEST_OPTS were visible in the build logs. > > I've found the output with 'set -x' sufficient so far, and don't think > that an explicit logging facility is worth it.
That's an interesting perspective. I would have thoguht that the values of these two variables we can see above, that are constants without any substitution or customization, are the least interesting things to see in the log.
