![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
vjuranek
|
|
Components:
|
ws-cleanup |
|
Created:
|
11/Nov/13 11:42 PM
|
|
Description:
|
Occasionally on our Windows 7 build nodes, when a $WORKSPACE fails to appear, the ws-cleanup plugin (post-build execution cleanup) will mark the job as failed even though it technically has succeeded because the workspace does not exist.
ws-cleanup should consider itself a success (and not alter the job status) if the $WORKSPACE no longer exists, NOT whether it succeeded itself in the deletion.
Here's an example of the console output
14:21:57 [EnvInject] - Loading node environment variables.
14:21:57 Building remotely on jrf-w7-ie8-5 in workspace c:\jenkins\workspace\JRF-Sanity-PeoplePlaces-UI-ie8-7c4
14:21:57
14:21:57 Deleting project workspace...
14:22:03 Cannot delete workspace: java.io.IOException: Remote call on jrf-w7-ie8-5 failed
14:22:03 ERROR: Cannot delete workspace: java.io.IOException: Remote call on jrf-w7-ie8-5 failed
14:22:03 Robot results publisher started...
14:22:03 -Parsing output xml:
14:22:03 Changing BUILD_ID variable (job build time) with the date pattern yyyyMMddHHmmss.
14:22:03 Changing BUILD_ID variable (job build time) with the date pattern yyyyMMddHHmmss.
14:22:03 Changing BUILD_ID variable (job build time) with the date pattern yyyyMMddHHmmss.
14:22:03 Changing BUILD_ID variable (job build time) with the date pattern yyyyMMddHHmmss.
14:22:03 Failed!
14:22:03 c:\jenkins\workspace\JRF-Sanity-PeoplePlaces-UI-ie8-7c4\target\robotframework does not exist.
14:22:03 at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:483)
14:22:03 at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:460)
14:22:03 at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:64)
14:22:03 at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:50)
14:22:03 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387)
14:22:03 at hudson.remoting.UserRequest.perform(UserRequest.java:118)
14:22:03 at hudson.remoting.UserRequest.perform(UserRequest.java:48)
14:22:03 at hudson.remoting.Request$2.run(Request.java:326)
14:22:03 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
14:22:03 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
14:22:03 at java.util.concurrent.FutureTask.run(Unknown Source)
14:22:03 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
14:22:03 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
14:22:03 at hudson.remoting.Engine$1$1.run(Engine.java:60)
14:22:03 at java.lang.Thread.run(Unknown Source)
14:22:03
14:22:03 Deleting project workspace...
14:22:03 Build step 'Delete workspace when build is done' marked build as failure
14:22:03 [BFA] Scanning build for known causes...
14:22:03
14:22:03 [BFA] Done. 0s
14:22:03 Notifying upstream projects of job completion
14:22:03 Finished: FAILURE
|
|
Environment:
|
CentOS 6 Jenkins Server, Windows 7 Build Node
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Eric Griswold
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
