On Wed, 11 Mar 2020 at 21:07, Elliotte Rusty Harold <[email protected]> wrote:
> On Tue, Mar 10, 2020 at 7:56 PM Olivier Lamy <[email protected]> wrote: > > > > Thanks Robert > > Anyway as the build only fail for jdk7 with mvn 3.2.5 on a particular > node > > of the asf machines. > > I build that perfectly with same jdk/mvn.... > > So we cannot really consider this as blocker... > > > > I absolutely do consider that a blocker. Even if it's something as > idiosyncratic as we need to turn one build machine off and on again, > this needs to be repaired before a release. Even when the failure mode > is not a true bug, a failing build trains developers to ignore > failures, which lets much more serious bugs creep in unnoticed. > ok no worries. So do you want to be volunteer try to understand the problem on this node and fix the problem with ASF infra folks? > > If you disable one failing test because of a build machine issue, what > happens when that test starts failing everywhere because of an > unrelated change? > I do not disable any test. I'm just saying only one build of the matrix fail (jdk7/mvn 3.2.5) The same test works on every other part of the matrix. And as I said I used the exactly same combination and it works > > I've been there before and it's not pretty. Reliable, non-flaky test > suites are critical for software development. CI systems should be as > automatic as possible, and should not be routed around. > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
