[JIRA] (JENKINS-46553) Maven surefire timeout treated as successful build

[f.mod...@gmx.net (JIRA)]

Title: Message Title

Falko Modler commented on JENKINS-46553   Re: Maven surefire timeout treated as successful build Plot twist: I don't think anymore that Jenkins is to blame, at least in my case: I am (and probably most other Jenkins users are) setting -Dmaven.test.failure.ignore=true to get all test results instead of a failing build after the first module with test failures. This is where https://issues.apache.org/jira/browse/SUREFIRE-953 comes into play! What we would need is another Maven Surefire property/feature, that differentiates between regular test failures and timeouts. For now I am using the following pipeline lib function which I just need to call in my pipelines (in some post block) without any parameters: // Parses the console log file for known errors (that Jenkins does not properly recognize as build failures) and fails the build if any are found. def call() { def known = [ 'There was a timeout or other error in the fork' // https://issues.jenkins-ci.org/browse/JENKINS-46553 ] def consoleLogFile = "${WORKSPACE}/../builds/${BUILD_NUMBER}/log" println "Checking for known errors in console log file that are not properly handled by Jenkins: ${consoleLogFile}" // grep the cosole log, notes: // - "set +x" to avoid echoing the grep command which would lead to a false positive // - "set +e" to avoid build failure due to non-zero exit code (otherwise "exit 0" wouldn't be reached) def foundErrors = sh(script: "set +xe && grep '${known.join('|')}' ${consoleLogFile}; exit 0", returnStdout: true) if (foundErrors != "") { error("Found known errors in the log (see previous outputs for more context):\n${foundErrors}") } } PS: Yes I know, directly "grepping" the log file is not good practise. I also haven't tested this with/on slaves. I do also know that there are log parsing plugins but they do come with their own litte quirks, bugs and overhead... Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184875.1504135901000.521.1568115000357%40Atlassian.JIRA.