{"thread":{"id":"39366","subject":"Re: sh -x -i -v with continuous integration, was Re: [PATCH 1/4] t7601: test for pull.ff=true overrides merge.ff=false","startedAt":"2015-05-19T13:22:49Z","lastAt":"2015-05-19T13:22:49Z","messageCount":1,"participants":["Johannes Schindelin"],"isPatch":true,"patchVersion":1,"patchTotal":4},"messages":[{"id":"261546","messageId":"dc9d4364b795ad0c9d128a9e0c06e681@www.dscho.org","threadId":"39366","inReplyTo":null,"subject":"Re: sh -x -i -v with continuous integration, was Re: [PATCH 1/4] t7601: test for pull.ff=true overrides merge.ff=false","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2015-05-19T13:22:49Z","receivedAt":"2015-05-19T13:22:49Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Paul,\n\nOn 2015-05-16 14:33, Paul Tan wrote:\n\n> On Fri, May 15, 2015 at 12:53 AM, Johannes Schindelin\n> <johannes.schindelin@gmx.de> wrote:\n>> 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.\n> \n> Would the --tee option work for this case?\n> \n>     --tee::\n>         In addition to printing the test output to the terminal,\n>         write it to files named 't/test-results/$TEST_NAME.out'.\n>         As the names depend on the tests' file names, it is safe to\n>         run the tests with this option in parallel.\n\nThanks for pointing this out to me. This is such a useful option.\n\nNow, who made that patch... Oh, wow, oops [*1*]. Time for a coffee, I guess.\n\nThank you!\nDscho\n\nFootnote *1*: https://github.com/git/git/commit/44138559e8b7c89768a2450220b831847059311c\n"}]}