Thread (192 messages) 192 messages, 13 authors, 2021-03-26

Re: [PATCH v2 10/13] tests: include detailed trace logs with --write-junit-xml upon failure

From: Johannes Schindelin <hidden>
Date: 2018-10-16 20:53:35

Hi Gábor,

On Tue, 16 Oct 2018, SZEDER Gábor wrote:
On Tue, Oct 16, 2018 at 03:02:38PM +0200, Johannes Schindelin wrote:
quoted
So I would suggest to go forward with my proposed strategy for the
moment, right up until the time when we have had the resources to fix
t5570, for starters.
I don't really understand what the occasional failures in t5570 have
to do with the amount of information a CI system should gather about
failures in general.
I see it plenty of times that too many CI failures essentially render
every developer numb.

If every 3rd CI run causes a failure, and seemingly every of these
failures indicates a mistake in the regression test, rather than a
regression, developers stop paying attention.

Which is the exact opposite of what I want to achieve here.

Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help