# Re: sh -x -i -v with continuous integration, was Re: [PATCH 1/4] t7601: test for pull.ff=true overrides merge.ff=false

1 messages from 2015-05-19 to 2015-05-19. Participants: Johannes Schindelin.
Thread: https://gitlist.dev/t/39366

## Johannes Schindelin, 2015-05-19 13:22

Subject: Re: sh -x -i -v with continuous integration, was Re: [PATCH 1/4] t7601: test for pull.ff=true overrides merge.ff=false
Message-ID: <dc9d4364b795ad0c9d128a9e0c06e681@www.dscho.org>
URL: https://gitlist.dev/e/dc9d4364b795ad0c9d128a9e0c06e681%40www.dscho.org

```
Hi Paul,

On 2015-05-16 14:33, Paul Tan wrote:

> On Fri, May 15, 2015 at 12:53 AM, Johannes Schindelin
> <johannes.schindelin@gmx.de> wrote:
>> Asketh and ye shall be given: without running the tests in parallel, our Jenkins would take *even longer* than the three hours per test suite run (which is really painful, still, by the way). And as you know, running the tests with "-v -x" is awfully useless if you run the test suite in parallel.
> 
> Would the --tee option work for this case?
> 
>     --tee::
>         In addition to printing the test output to the terminal,
>         write it to files named 't/test-results/$TEST_NAME.out'.
>         As the names depend on the tests' file names, it is safe to
>         run the tests with this option in parallel.

Thanks for pointing this out to me. This is such a useful option.

Now, who made that patch... Oh, wow, oops [*1*]. Time for a coffee, I guess.

Thank you!
Dscho

Footnote *1*: https://github.com/git/git/commit/44138559e8b7c89768a2450220b831847059311c

```
