Re: [PATCH 0/3] making test-suite tracing more useful
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Oct 23, 2017, 11:04 UTC
- Message-ID
- <alpine.DEB.2.21.1.1710231302480.6482@virtualbox>
- In-Reply-To
- <20171019210140.64lb52cqtgdh22ew@sigill.intra.peff.net>
Hi Peff,
On Thu, 19 Oct 2017, Jeff King wrote:
> I sometimes run git's test suite as part of an automated testing > process. I was hoping to add "-x" support to get more details when a > test fails (since failures are sometimes hard to reproduce).
Thank you for working on this.
Show 5 quoted lines
> Johannes, I've seen that you do "-x" in the tests that the > git-for-windows bot uses to comment on GitHub. You may have seen the > bogus failure in t5615, which this series should fix (you may also have > seen the "set +x" cruft at the end of each test, which is fixed here, > too).
Surprisingly enough, I did not see any test failure in that test. I do re-run failed tests after the complete test run to make sure that the failure is not due to any resource scarcity, and that re-run is performed with -x (to double as documentation what really went wrong).
Ciao, Dscho