[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view

[r.fuere...@xortex.com (JIRA)]

Title: Message Title

Reinhold Füreder commented on JENKINS-46715   Re: Error steps may change to show up as errors in pipeline view Thorsten Scherler First of all thanks a lot in advance for taking care of this mysterious and disturbing problem The classic UI shows the error as expected: Of course the build itself is red (but this is also the case in BO) The console log contains the error step output at the very end: ... > Task :migrateDb FAILEDFAILURE: Build failed with an exception.* What went wrong: Execution failed for task ':migrateDb'. > Process 'command 'php'' finished with non-zero exit value 1* Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at https://help.gradle.orgBUILD FAILED in 14s 2 actionable tasks: 1 executed, 1 up-to-date [Pipeline] echo [DEBUG] gradlew phpunit exit code: 1 [Pipeline] pwd [Pipeline] error [Pipeline] } $ docker stop --time=1 2d13f6eb6583a72e93035a276888210f140b200ab6e7533144bf017ad1f13965 $ docker rm -f 2d13f6eb6583a72e93035a276888210f140b200ab6e7533144bf017ad1f13965 [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // withDockerRegistry [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] sh [ACME-Pipeline-WS] Running shell script + docker stop d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b + docker rm -f d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b [Pipeline] } [Pipeline] // withDockerRegistry [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] ansiColor [Pipeline] { [Pipeline] echo Pipeline problem: PHPUnit DB integration test execution failed completely due to: "hudson.AbortException: PHPUnit DB integration test execution failed completely: Please check the previous step(s)" => Please check the "Console/Log Output" => Failure notification will be sent... [Pipeline] } [Pipeline] // ansiColor [Pipeline] emailextrecipients [Pipeline] emailextrecipients [Pipeline] emailextrecipients [Pipeline] emailextrecipients [Pipeline] emailextrecipients [Pipeline] emailextrecipients [Pipeline] echo email-ext-recipients: failingTestSuspects: failingBuildSuspects: developers: a.n...@acme.com culprits: a.n...@acme.com requester: upstreamCommitters: [Pipeline] emailext Single culprit: [A Name] Sending email to: a.n...@acme.com jenkins.ci...@acme.com [Pipeline] stage [Pipeline] { (kpi) [Pipeline] echo Listing all KPIs... [Pipeline] echo[Pipeline] node Running on Jenkins in /var/lib/jenkins/workspace/ACME-Pipeline [Pipeline] { [Pipeline] ws Running in /var/lib/jenkins/workspace/ACME-Pipeline-WS-kpi [Pipeline] { [Pipeline] echo Build Pipeline KPIs: - Build duration: 2 minutes, 49.844 seconds ... time duration since build start - Time duration since build scheduling: 2 minutes, 49.857 seconds - Pipeline net execution time duration: 2 minutes, 42.368 seconds ... in "acme.build" - Cycle time: 2 minutes, 50.570 seconds ... time duration since (oldest included production code) SVN commit (170953) [Pipeline] echo Stage completion times ... time between SVN commit and end of stage: - "checkout": 1 minutes, 33.175 seconds - "docker-unit-tests": 2 minutes, 7.690 seconds - "docker-db-integration-tests": 2 minutes, 47.984 seconds [Pipeline] pwd [Pipeline] plot [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline ERROR: PHPUnit DB integration test execution failed completely: Please check the previous step(s) Finished: FAILURE And in "Pipeline Steps" view it shows:   For this build BO actually looks like this: That is, it does not highlight the failing stage, and presumably therefore also does not auto-scroll to the error step?   Do you need anything else? (I will look for other recent occurrences to check if they are consistent with this one.) Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.