[JIRA] (JENKINS-56978) The pipeline status sometimes not appear in output

2 views
Skip to first unread message

shurikgefter@gmail.com (JIRA)

unread,
Apr 11, 2019, 11:13:02 AM4/11/19
to jenkinsc...@googlegroups.com
Shurik Gefter created an issue
 
Jenkins / Bug JENKINS-56978
The pipeline status sometimes not appear in output
Issue Type: Bug Bug
Assignee: Unassigned
Components: jenkinsfile-runner
Created: 2019-04-11 15:12
Priority: Minor Minor
Reporter: Shurik Gefter

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

"Finished: FAILURE"
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

m.vilacides@gmail.com (JIRA)

unread,
Apr 12, 2019, 4:21:02 AM4/12/19
to jenkinsc...@googlegroups.com
Isa Vilacides commented on Bug JENKINS-56978
 
Re: The pipeline status sometimes not appear in output

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

shurikgefter@gmail.com (JIRA)

unread,
Apr 14, 2019, 8:52:08 AM4/14/19
to jenkinsc...@googlegroups.com

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

egutierrez@cloudbees.com (JIRA)

unread,
Apr 16, 2019, 2:59:03 AM4/16/19
to jenkinsc...@googlegroups.com

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?

egutierrez@cloudbees.com (JIRA)

unread,
Apr 16, 2019, 2:59:03 AM4/16/19
to jenkinsc...@googlegroups.com

shurikgefter@gmail.com (JIRA)

unread,
Apr 16, 2019, 3:30:02 AM4/16/19
to jenkinsc...@googlegroups.com
Shurik Gefter commented on Bug JENKINS-56978
 
Re: The pipeline status sometimes not appear in output

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

 

jglick@cloudbees.com (JIRA)

unread,
Jul 1, 2019, 10:08:02 AM7/1/19
to jenkinsc...@googlegroups.com

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.

Reply all
Reply to author
Forward
0 new messages