-
Bug
-
Resolution: Fixed
-
Minor
-
None
If there is a configuration problem with the job such that the code could not be checked out, the tap plugin still attempts to process the results. The build plugins manage to detect this and avoid running, shouldn't tap be able to do so as well?
Started by user Andrew Johnson Building remotely on cyg64-1 in workspace C:/cygwin64/home/jenkins/workspace/epics-base-3.15-cyg64 Cleaning workspace... $ bzr branch lp:epics-base/3.15/ C:/cygwin64/home/jenkins/workspace/epics-base-3.15-cyg64 Host key verification failed. Host key verification failed. ConnectionReset reading response for 'BzrDir.open_2.1', retrying bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist. ERROR: Failed to branch lp:epics-base/3.15/ TAP Reports Processing: START Looking for TAP results report in workspace using pattern: src/**/O.cygwin-x86_64/*.tap ERROR: Publisher org.tap4j.plugin.TapPublisher aborted due to exception C:\cygwin64\home\jenkins\workspace\epics-base-3.15-cyg64 does not exist. at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:483) at hudson.FilePath.glob(FilePath.java:1559) at hudson.FilePath.access$700(FilePath.java:168) at hudson.FilePath$26.invoke(FilePath.java:1537) at hudson.FilePath$26.invoke(FilePath.java:1534) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Sending e-mails to: xxx@xxx Finished: FAILURE