[JIRA] [sauce-ondemand-plugin] (JENKINS-32728) NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)

[costescuandrei@skymail.ro (JIRA)]

Andrei Costescu created an issue

Jenkins / JENKINS-32728 NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName) Issue Type: Bug Assignee: Jack Moxon Components: sauce-ondemand-plugin Created: 02/Feb/16 1:33 PM Environment: Jenkins ver. 1.619 Sauce plugin 1.129 Priority: Minor Reporter: Andrei Costescu The job runs, all tests pass, sauce job also looks normal/success.. Jenkins job reports Build Success and the tests reports show all passed. Even so the job is marked as a failure. I looked in the logs an I noticed this - which might be the culprit. Feb 01, 2016 8:09:40 PM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl$TimeoutTimerTask@68416dbd failed java.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.getCurrentHostName(SauceOnDemandBuildWrapper.java:466) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.access$600(SauceOnDemandBuildWrapper.java:78) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.getHostName(SauceOnDemandBuildWrapper.java:340) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:317) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:944) at hudson.plugins.build_timeout.operations.WriteDescriptionOperation.perform(WriteDescriptionOperation.java:65) at hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl$TimeoutTimerTask.doRun(BuildTimeoutWrapper.java:142) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Decremented process count for ..., now 0 Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Flushing Sauce Connect Input Stream Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Flushing Sauce Connect Error Stream Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Closing Sauce Connect process Feb 01, 2016 8:12:06 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Sauce Connect stopped for: ... Feb 01, 2016 8:12:06 PM hudson.model.Run execute INFO: my_job #1118 main build action completed: FAILURE I noticed there are newer versions which I might test, but I didn't see anything like this mentioned as fixed in the changelogs. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[costescuandrei@skymail.ro (JIRA)]

Andrei Costescu updated an issue

Jenkins / JENKINS-32728 NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)

Change By: Andrei Costescu

The job runs, all tests pass, sauce job also looks normal/success..

Jenkins job reports Build Success  in console  and the tests reports show all passed.

Even so the job is marked as a failure. I looked in the logs an I noticed this - which might be the culprit.

{code}Feb 01, 2016 8:09:40 PM hudson.triggers.SafeTimerTask run

SEVERE: Timer task hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl$TimeoutTimerTask@68416dbd failed java.lang.NullPointerException         at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.getCurrentHostName(SauceOnDemandBuildWrapper.java:466)         at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.access$600(SauceOnDemandBuildWrapper.java:78)         at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.getHostName(SauceOnDemandBuildWrapper.java:340)         at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:317)         at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:944)         at hudson.plugins.build_timeout.operations.WriteDescriptionOperation.perform(WriteDescriptionOperation.java:65)         at hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl$TimeoutTimerTask.doRun(BuildTimeoutWrapper.java:142)         at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)         at java.util.TimerThread.mainLoop(Timer.java:555)         at java.util.TimerThread.run(Timer.java:505) Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Decremented process count for ..., now 0 Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Flushing Sauce Connect Input Stream Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Flushing Sauce Connect Error Stream Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Closing Sauce Connect process Feb 01, 2016 8:12:06 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessage INFO: Sauce Connect stopped for: ... Feb 01, 2016 8:12:06 PM hudson.model.Run execute INFO: my_job #1118 main build action completed: FAILURE

{code}

I noticed there are newer versions which I might test, but I didn't see anything like this mentioned as fixed in the changelogs.

Add Comment

[costescuandrei@skymail.ro (JIRA)]

Andrei Costescu commented on JENKINS-32728

Re: NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName) I think I found an explanation. Builds that failed took > 40 min (42 min for example). And the build timeout plugin is configured at 40 min. I noticed that the builds that pass are 39m, 38m, or even some of the 40m ... (others with 40m fail) So it times out close to job's normal end time. Maybe right when sauce plugin does it's cleanup. But it's strange that I don't get notified that it timed out in the console or somewhere (in job history as usual for example). Maybe that is caused by this NPE.

Add Comment

[halkeye@gmail.com (JIRA)]

Gavin Mogan commented on JENKINS-32728

Re: NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)

Andrei A I would recommend upgrading and checking if its still a problem. There has been some major refactoring done since then and hopefully should fix things.

Add Comment

[halkeye@gmail.com (JIRA)]

Gavin Mogan resolved as Incomplete

Jenkins / JENKINS-32728

NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)

Change By: Gavin Mogan Status: Open Resolved Resolution: Incomplete

Add Comment

[halkeye@gmail.com (JIRA)]

Gavin Mogan assigned an issue to Gavin Mogan

Jenkins / JENKINS-32728 NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)

Change By: Gavin Mogan Assignee: Jack Moxon Gavin Mogan

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)