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 <rfscho...@apache.org> 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 <elh...@ibiblio.org> 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 > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
