Looks like the magic words are "pipeline steps". Why that isn't linked directly from the failures and why one has to go hunting through inobviously named menus, I don't know; but that's a Jenkins issue, not a Maven one. I do think it would be worth revisiting our choice of CI servers one of these days. Jenkins has fallen far behind the state of the art, but that's a subject for another thread.
On Thu, Dec 31, 2020 at 11:48 AM Bernd Eckenfels <[email protected]> wrote: > > Hello, > > As long as we have windows builds and jdk15+ builds I guess one can reduce > the flaky combinations but it would still be interesting to see what’s the > problem is, in the pipeline steps view you see the failed step > > https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/null/2/flowGraphTable/ > > And it’s console log > > https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/null/2/execution/node/315/log/ > > I complains about a unexpected dependency tree (this does not really look > platform-version specific, maybe more a repository issue?) > > Gruss > Bernd > -- > http://bernd.eckenfels.net > ________________________________ > Von: Elliotte Rusty Harold <[email protected]> > Gesendet: Thursday, December 31, 2020 12:37:18 PM > An: Maven Developers List <[email protected]> > Betreff: Re: Build windows-jdk15 > > Here's one example: > > https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/null/ > > There are many others. Nothing changed between the three runs. First > Windows JDK 15 failed. Then Windows JDK 7 failed. Then they all > passed. No code changes were made between the runs. If there's a way > to see the logs from the failed runs, it's far from obvious to me. > > Flaky build infrastructure is dangerous because it teaches developers > to ignore the CI. > > > > > On Wed, Dec 30, 2020 at 11:38 PM Robert Scholte <[email protected]> wrote: > > > > What's you analysis? > > Did you inform INFRA? > > If we have issues with these versions, most likely Maven users will have to. > > > > We've seen this in the past too and I think all the time I'm been able to > > bring the builds back to blue. > > Disabling would be avoiding or ignoring the problem. > > > > thanks, > > Robert > > On 30-12-2020 14:59:16, Elliotte Rusty Harold <[email protected]> wrote: > > The Windows JDK 15 instance in jenkins seems irredeemably flaky. It > > fails more often than not for reasons that have nothing to do with the > > code being tested. > > > > As JDK 15 is not a long term support release, and has only minimal > > adoption, can we simply turn off the Windows JDK 15 build? > > > > Personally, I'd love to turn off all JDK 15 and 16 builds, but Windows > > JDK 15 is by far the worst. > > > > -- > > Elliotte Rusty Harold > > [email protected] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
