Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

Hi Peff, On Wed, 5 Sep 2018, Jeff King wrote: > On Wed, Sep 05, 2018 at 02:38:34PM -0400, Eric Sunshine wrote: > > > On Wed, Sep 5, 2018 at 8:39 AM Johannes Schindelin > > wrote: > > > So let's hear some ideas how to improve the situation, m'kay? Just > > > as a reminder, this is the problem

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

Hi Eric, On Wed, 5 Sep 2018, Eric Sunshine wrote: > On Wed, Sep 5, 2018 at 8:39 AM Johannes Schindelin > wrote: > > So let's hear some ideas how to improve the situation, m'kay? Just as > > a reminder, this is the problem I want to solve: I want to run the > > tests in a light-weight manner,

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

Hi Luke, On Wed, 5 Sep 2018, Luke Diamand wrote: > On 5 September 2018 at 13:39, Johannes Schindelin > wrote: > > > > On Wed, 5 Sep 2018, Luke Diamand wrote: > > > >> On 4 September 2018 at 12:09, Johannes Schindelin > >> wrote: > >> > > >> > On Tue, 4 Sep 2018, Eric Sunshine wrote: > >> > >

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

On Wed, Sep 05, 2018 at 02:38:34PM -0400, Eric Sunshine wrote: > On Wed, Sep 5, 2018 at 8:39 AM Johannes Schindelin > wrote: > > So let's hear some ideas how to improve the situation, m'kay? > > Just as a reminder, this is the problem I want to solve: I want to run the > > tests in a

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

On Wed, Sep 5, 2018 at 8:39 AM Johannes Schindelin wrote: > So let's hear some ideas how to improve the situation, m'kay? > Just as a reminder, this is the problem I want to solve: I want to run the > tests in a light-weight manner, with minimal output, and only in case of > an error do I want to

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

On 5 September 2018 at 13:39, Johannes Schindelin wrote: > Hi Luke, > > On Wed, 5 Sep 2018, Luke Diamand wrote: > >> On 4 September 2018 at 12:09, Johannes Schindelin >> wrote: >> > >> > On Tue, 4 Sep 2018, Eric Sunshine wrote: >> > >> >> On Mon, Sep 3, 2018 at 5:10 PM Johannes Schindelin via

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

Hi Luke, On Wed, 5 Sep 2018, Luke Diamand wrote: > On 4 September 2018 at 12:09, Johannes Schindelin > wrote: > > > > On Tue, 4 Sep 2018, Eric Sunshine wrote: > > > >> On Mon, Sep 3, 2018 at 5:10 PM Johannes Schindelin via GitGitGadget > >> wrote: > >> > So let's do something different in

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

On 4 September 2018 at 12:09, Johannes Schindelin wrote: > Hi Eric, > > On Tue, 4 Sep 2018, Eric Sunshine wrote: > >> On Mon, Sep 3, 2018 at 5:10 PM Johannes Schindelin via GitGitGadget >> wrote: >> > So let's do something different in VSTS: let's run all the tests with >> > `--quiet` first, and

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

Hi Eric, On Tue, 4 Sep 2018, Eric Sunshine wrote: > On Mon, Sep 3, 2018 at 5:10 PM Johannes Schindelin via GitGitGadget > wrote: > > So let's do something different in VSTS: let's run all the tests with > > `--quiet` first, and only if a failure is encountered, try to trace the > > commands as

Re: [PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

On Mon, Sep 3, 2018 at 5:10 PM Johannes Schindelin via GitGitGadget wrote: > So let's do something different in VSTS: let's run all the tests with > `--quiet` first, and only if a failure is encountered, try to trace the > commands as they are executed. [...] > > Signed-off-by: Johannes

[PATCH 7/9] tests: include detailed trace logs with --write-junit-xml upon failure

From: Johannes Schindelin The JUnit XML format lends itself to be presented in a powerful UI, where you can drill down to the information you are interested in very quickly. For test failures, this usually means that you want to see the detailed trace of the failing tests. With Travis CI, we