[JIRA] (JENKINS-58981) Successful build marked as failed

[luk355@gmail.com (JIRA)]

Lukas Behal created an issue

Jenkins / JENKINS-58981 Successful build marked as failed Issue Type: Bug Assignee: Unassigned Attachments: image-2019-08-19-14-44-52-341.png Components: core Created: 2019-08-19 03:07 Environment: OS: MS Windows server 2012 R2 Java version: 1.8.0_144-b01 (Oracle corp) Jenkins version: 2.176.2 Web browser: Chrome v76.0.3809.100 this build is using Performance Plugin 3.17 All plugins: ace-editor 1.1 active-directory 2.16 allure-jenkins-plugin 2.28.1 analysis-core 1.96 analysis-model-api 5.3.0 ansicolor 0.6.1 ant 1.9 antisamy-markup-formatter 1.5 apache-httpcomponents-client-4-api 4.5.5-3.0 authentication-tokens 1.3 authorize-project 1.3.0 badge 1.8 bitbucket-approve 1.0.3 bitbucket-build-status-notifier 1.4.1 bitbucket-oauth 0.9 blueocean-commons 1.18.1 blueocean-config 1.18.1 blueocean-core-js 1.18.1 blueocean-dashboard 1.18.1 blueocean-display-url 2.3.0 blueocean-i18n 1.18.1 blueocean-jira 1.18.1 blueocean-jwt 1.18.1 blueocean-personalization 1.18.1 blueocean-pipeline-scm-api 1.18.1 blueocean-rest 1.18.1 blueocean-rest-impl 1.18.1 blueocean-web 1.18.1 bouncycastle-api 2.17 branch-api 2.5.4 build-failure-analyzer 1.22.0 build-history-metrics-plugin 1.2 build-name-setter 2.0.1 build-pipeline-plugin 1.5.8 build-publisher 1.22 build-time-blame 1.2.0 build-timeout 1.19 build-user-vars-plugin 1.5 build-with-parameters 1.4 checkmarx 8.90.4 chucknorris 1.2 claim 2.15 cloudbees-bitbucket-branch-source 2.4.5 cloudbees-folder 6.9 cobertura 1.14 code-coverage-api 1.0.13 command-launcher 1.3 conditional-buildstep 1.3.6 config-file-provider 3.6.2 copyartifact 1.42.1 credentials 2.2.1 credentials-binding 1.20 cucumber-living-documentation 2.2.2 cucumber-reports 4.8.0 dashboard-view 2.11 delivery-pipeline-plugin 1.3.1 disk-usage 0.28 display-url-api 2.3.2 docker-commons 1.15 docker-workflow 1.19 downstream-buildview 1.9 dtkit-api 2.1.1-1 durable-task 1.30 email-ext 2.66 emailext-template 1.1 embeddable-build-status 2.0.2 envinject 2.2.0 envinject-api 1.6 external-monitor-job 1.7 extra-columns 1.20 favorite 2.3.2 flyway-runner 1.9 git 3.11.0 git-client 3.0.0-rc git-parameter 0.9.11 git-server 1.8 github-api 1.95 global-build-stats 1.5 gradle 1.33 greenballs 1.15 groovy 2.2 groovy-postbuild 2.5 handlebars 1.1.1 handy-uri-templates-2-api 2.1.7-1.0 htmlpublisher 1.18 hudson-pview-plugin 1.8 jackson2-api 2.9.9.1 javadoc 1.5 jdk-tool 1.3 jenkins-design-language 1.18.1 jenkins-flowdock-plugin 1.1.8 jira 3.0.8 job-dsl 1.74 job-restrictions 0.8 jobConfigHistory 2.23.1 jobrequeue 1.1 join 1.21 jquery 1.12.4-0 jquery-detached 1.2.1 jquery-ui 1.0.2 jsch 0.1.55.1 junit 1.28 ldap 1.20 lockable-resources 2.5 mailer 1.24 mapdb-api 1.0.9.0 mask-passwords 2.12.0 matrix-auth 2.4.2 matrix-project 1.14 maven-plugin 3.4 mercurial 2.8 metrics 4.0.2.5 metrics-diskusage 3.0.0 mission-control-view 0.9.14 momentjs 1.1.1 monitoring 1.79.0 msbuild 1.29 mstest 1.0.0 multiple-scms 0.6 naginator 1.18 nodejs 1.3.3 nunit 0.25 Office-365-Connector 4.11.0 ownership 0.12.1 pam-auth 1.5.1 Parameterized-Remote-Trigger 3.0.8 parameterized-trigger 2.35.2 performance 3.17 perfpublisher 8.09 pipeline-aggregator-view 1.8 pipeline-build-step 2.9 pipeline-graph-analysis 1.10 pipeline-input-step 2.10 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.9 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.9 pipeline-model-extensions 1.3.9 pipeline-rest-api 2.12 pipeline-stage-step 2.3 pipeline-stage-tags-metadata 1.3.9 pipeline-stage-view 2.12 plain-credentials 1.5 postbuildscript 2.8.1 powershell 1.3 pubsub-light 1.12 rally-plugin 2.2.2 rebuild 1.29 resource-disposer 0.13 role-strategy 2.13 run-condition 1.2 scm-api 2.6.3 scm-sync-configuration 0.0.10 script-security 1.62 sloccount 1.24 sse-gateway 1.19 ssh-agent 1.17 ssh-credentials 1.17.1 ssh-slaves 1.30.1 stash-pullrequest-builder 1.12 stashNotifier 1.19 structs 1.20 subversion 2.12.2 thinBackup 1.9 throttle-concurrents 2.0.1 timestamper 1.10 token-macro 2.8 trilead-api 1.0.3 variant 1.3 view-job-filters 2.1.1 violation-comments-to-stash 1.109 warnings-ng 5.3.0 windows-slaves 1.4 workflow-aggregator 2.6 workflow-api 2.36 workflow-basic-steps 2.18 workflow-cps 2.73 workflow-cps-global-lib 2.15 workflow-durable-task-step 2.33 workflow-job 2.33 workflow-multibranch 2.21 workflow-scm-step 2.9 workflow-step-api 2.20 workflow-support 3.3 ws-cleanup 0.37 xfpanel 2.0.1 xunit 2.3.5 Priority: Minor Reporter: Lukas Behal Successfully finished builds are marked as Failed. Console output: ... 13:36:22 Archiving artifacts 13:36:22 Recording fingerprints 13:36:22 Creating parser with percentiles:'0,50,90,100,' filterRegex:null 13:36:22 Performance: Recording JMeterCsv reports '_test_results\jmeter_tests\*.jtl' 13:36:22 Performance: JMeterCsv copying reports to master, files '[E:\x.jtl]' 13:36:22 Performance: JMeterCsv parsing local reports '[C:\x.jtl]' 13:36:22 Performance: Parsing report file 'C:\x.jtl' with filterRegex 'null'. 13:36:22 Performance: Percentage of errors greater or equal than 1% sets the build as unstable 13:36:22 Performance: Percentage of errors greater or equal than 2% sets the build as failure 13:36:22 Performance: File JMeterTestsResults.jtl reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS 13:36:22 Disk usage plugin fails during calculation disk usage of this build. 13:36:22 Notifying upstream projects of job completion 13:36:22 Finished: SUCCESS This build is displayed in Jenkins as: I tried to search where the build status is stored on file system and found following record in all_builds.mr in the jobs folder. ... 67,1566178385513,197137,SUCCESS This issue is intermittent. I would really appreciate any help.             Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[luk355@gmail.com (JIRA)]

Lukas Behal updated an issue

Jenkins / JENKINS-58981 Successful build marked as failed

Change By: Lukas Behal Successfully finished builds are marked as Failed. The build is using Performance Console output: {code:java}

... 13:36:22 Archiving artifacts 13:36:22 Recording fingerprints 13:36:22 Creating parser with percentiles:'0,50,90,100,' filterRegex:null 13:36:22 Performance: Recording JMeterCsv reports '_test_results\jmeter_tests\*.jtl' 13:36:22 Performance: JMeterCsv copying reports to master, files '[E:\x.jtl]' 13:36:22 Performance: JMeterCsv parsing local reports '[C:\x.jtl]' 13:36:22 Performance: Parsing report file 'C:\x.jtl' with filterRegex 'null'. 13:36:22 Performance: Percentage of errors greater or equal than 1% sets the build as unstable 13:36:22 Performance: Percentage of errors greater or equal than 2% sets the build as failure 13:36:22 Performance: File JMeterTestsResults.jtl reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS 13:36:22 Disk usage plugin fails during calculation disk usage of this build. 13:36:22 Notifying upstream projects of job completion 13:36:22 Finished: SUCCESS

{code}

This build is displayed in Jenkins as:

!image-2019-08-19-14-44-52-341.png! I tried to search where the build status is stored on file system and found following record in _all_builds.mr_ in the jobs folder. {code:java} ... 67,1566178385513,197137,SUCCESS {code}

This issue is intermittent. I would really appreciate any help.

Add Comment

[luk355@gmail.com (JIRA)]

Lukas Behal updated an issue

Jenkins / JENKINS-58981 Successful build marked as failed Change By: Lukas Behal

Successfully finished builds are marked as Failed. The build is using Performance Plugin.

[luk355@gmail.com (JIRA)]

Update: I did notice that

Add Comment

[luk355@gmail.com (JIRA)]

I did notice that all build.xml files of the jobs with this intermittent issue are missing <result> xml tag as opposed to others.   These jobs are being run on remote agent. Could this be relevant to this issue?

Add Comment