Project

General

Profile

Actions

Bug #3637

closed

OSX-10.10-ucla-pistons-10014 remote file operation failed

Added by Junxiao Shi over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Immediate
Category:
Build
Target version:
Start date:
05/26/2016
Due date:
% Done:

0%

Estimated time:
3.00 h

Description

There are higher than normal build failures on OSX-10.10-ucla-pistons-10014 slave.

Error message looks like:

ERROR: Step ‘Publish xUnit test result report’ aborted due to exception: 
java.io.IOException: remote file operation failed: /Users/jenkins/workspace/ndn-tools/OS/OSX-10.10 at hudson.remoting.Channel@3bca9046:OSX-10.10-ucla-pistons-10014: java.io.IOException: Remote call on OSX-10.10-ucla-pistons-10014 failed
    at hudson.FilePath.act(FilePath.java:986)
    at hudson.FilePath.act(FilePath.java:968)
    at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:145)
    at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(XUnitProcessor.java:88)
    at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:142)
    at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:134)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
    at hudson.model.Build$BuildExecution.post2(Build.java:185)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
    at hudson.model.Run.execute(Run.java:1763)
    at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)
Actions #1

Updated by Junxiao Shi over 8 years ago

  • Priority changed from Normal to Immediate
  • Estimated time set to 3.00 h

This slave should be taken offline immediately, because none of the builds assigned to this node has been successful since May 26.

After taken offline, the priority of this issue can be lowered to High for repairing this slave.

Actions #2

Updated by Junxiao Shi over 8 years ago

  • Status changed from New to Closed

It seems that this slave has been fixed.

Actions

Also available in: Atom PDF