Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56978

The pipeline status sometimes not appear in output

    Details

    • Similar Issues:

      Description

      I run the same Jenkinfile via docker and sometimes the status of pipeline not present in output

      "Finished: FAILURE"
      

        Attachments

          Issue Links

            Activity

            Hide
            vilacides Isa Vilacides added a comment -

            Shurik Gefter could you please provide steps to reproduce? there are automated tests validating this scenario, so it must be a specific configuration you have or something being done differently. With the current information there is nothing we can do to help. Thanks

            Show
            vilacides Isa Vilacides added a comment - Shurik Gefter could you please provide steps to reproduce? there are automated tests validating this scenario, so it must be a specific configuration you have or something being done differently. With the current information there is nothing we can do to help. Thanks
            Hide
            shurikg Shurik Gefter added a comment -

            I doesn't know how to reproduce the problem.

            I use the runner to test my shared library and one of my asset is that I have in console output:

            "Finished: FAILURE"
            

            in code I have

                self.assertMessageInLog("Finished: FAILURE", output)
            

            Now, when I run the same test 10 times, 8 times it's passed and 2 failed while the test code and shared lib not changed in SCM.

            Normal execution

            [Pipeline] // timestamps
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // withEnv
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] End of Pipeline
            ERROR: [ERROR] [undefined_parameter] is not a valid method parameter
            
            Finished: FAILURE
            
            

            Problematic execution

            [Pipeline] // timestamps
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // withEnv
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] End of Pipeline
            
            
            Show
            shurikg Shurik Gefter added a comment - I doesn't know how to reproduce the problem. I use the runner to test my shared library and one of my asset is that I have in console output: "Finished: FAILURE" in code I have self.assertMessageInLog( "Finished: FAILURE" , output) Now, when I run the same test 10 times, 8 times it's passed and 2 failed while the test code and shared lib not changed in SCM. Normal execution [Pipeline] // timestamps [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: [ERROR] [undefined_parameter] is not a valid method parameter Finished: FAILURE Problematic execution [Pipeline] // timestamps [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline
            Hide
            egutierrez Evaristo Gutierrez added a comment -

            Shurik Gefter thanks for providing some details!  I can see an error is raised in the pipeline you are using when the execution is fine. Do you experience the issue also when the pipeline finishes successfully?

            Show
            egutierrez Evaristo Gutierrez added a comment - Shurik Gefter thanks for providing some details!  I can see an error is raised in the pipeline you are using when the execution is fine. Do you experience the issue also when the pipeline finishes successfully?
            Hide
            shurikg Shurik Gefter added a comment -

            Hi,

            I did double check about the problem and it's exists in any case (success or failure)

            Please see below the example for both situation:

            For success message

            Build #59 - good execution

            [2019-04-10T13:56:58.590Z] [amd_helm_chart_release][INFO] helm release script finished successfully
            [Pipeline] }
            [Pipeline] // timestamps
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // withEnv
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] End of Pipeline
            Finished: SUCCESS
            

            Build #60 - regression

            [2019-04-10T14:07:40.587Z] [amd_helm_chart_release][INFO] helm release script finished successfully
            [Pipeline] }
            [Pipeline] // timestamps
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // withEnv
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] End of Pipeline
            

             
            As you can see the Finished: SUCCESS is missing

            For failure message

            Build #59 - good execution

            [2019-04-10T13:58:27.648Z] [amd_helm_chart_release][ERROR] helm release script failed
            [Pipeline] }
            [Pipeline] // timestamps
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // withEnv
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] End of Pipeline
            Finished: FAILURE
            

            Build #60 - regression

            [2019-04-10T14:09:06.858Z] [amd_helm_chart_release][ERROR] helm release script failed
            [Pipeline] }
            [Pipeline] // timestamps
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // withEnv
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] End of Pipeline
            

            As you can see the Finished: FAILURE is missing

            In the build #61 all tests passed without code change

             

            Show
            shurikg Shurik Gefter added a comment - Hi, I did double check about the problem and it's exists in any case (success or failure) Please see below the example for both situation: For success message Build #59 - good execution [2019-04-10T13:56:58.590Z] [amd_helm_chart_release][INFO] helm release script finished successfully [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS Build #60 - regression [2019-04-10T14:07:40.587Z] [amd_helm_chart_release][INFO] helm release script finished successfully [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline   As you can see the Finished: SUCCESS is missing For failure message Build #59 - good execution [2019-04-10T13:58:27.648Z] [amd_helm_chart_release][ERROR] helm release script failed [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: FAILURE Build #60 - regression [2019-04-10T14:09:06.858Z] [amd_helm_chart_release][ERROR] helm release script failed [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline As you can see the Finished: FAILURE is missing In the build #61 all tests passed without code change  
            Hide
            jglick Jesse Glick added a comment -

            Does sound like a race condition in JFR which would either be solved by updating to workflow-job from JENKINS-46076, or by doing that update and also changing the check used to close the process.

            Show
            jglick Jesse Glick added a comment - Does sound like a race condition in JFR which would either be solved by updating to workflow-job from JENKINS-46076 , or by doing that update and also changing the check used to close the process.

              People

              • Assignee:
                Unassigned
                Reporter:
                shurikg Shurik Gefter
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: