dweiss opened a new issue, #12565: URL: https://github.com/apache/lucene/issues/12565
### Description When a test fails in jenkins, it reports the gradle's build step as "build success" in the log file, even though some tests have failed. It's done so that all of the build runs until completion, then the CI (jenkins) will inspect build result files and fail at a higher level. In Uwe's own words: The tests.haltonfailure was added back, as it was heavily used by Jenkins. [...] Jenkins wants to differentiate between "build passed, but test failures" vs. "build did not pass due to compile failure, verifications". haltonfailure just reconfigures (like in ant) that the test runner does not exit the whole build with non-success exit code. Jenkins does not rely on exit code, it monitors test result xml files. This makes sense in a CI world. But I think we should omit printing this flag in the "reproduce with" line as it's confusing for people? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
