We now have 12 red and 1 yellow job in Jenkins: https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-master-jobs.html
Furthermore the number seems to be increasing over time. This block progress in multiple plugins. I haven't looked into each one, but the ones I've spot checked have all shown "no failures" and typically fail in some late message such as [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE That is, these appear to be build node failures rather than actual test failures. Is there anything that can be done systematically to prevent this? E.g. is there some way we can fix the root cause of the flakiness on build nodes? Or can we work around it by configuring Jenkins to accept "no failures" as success even if the script returns exit code 1? -- 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
