# Pastebin T4d4dHfU
Started by upstream project "node-test-binary-arm" build number 11622
originally caused by:
 Started by upstream project "node-test-commit-arm-fanned" build number 12407
 originally caused by:
  Started by upstream project "node-test-commit" build number 13851
  originally caused by:
   Started by upstream project "node-daily-v4.x-staging" build number 451
   originally caused by:
    Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on test-requireio_continuationlabs-debian7-arm_pi1p-1 (pi1-raspbian-wheezy) in workspace /home/iojs/build/workspace/node-test-binary-arm
[node-test-binary-arm] $ /bin/sh -xe /tmp/jenkins4425739269158938559.sh
+ set +x
Wed Nov 8 09:05:16 UTC 2017
+ pgrep node
21393
[node-test-binary-arm] $ /bin/bash -ex /tmp/jenkins2126587330713844364.sh
+ rm -rf RUN_SUBSET
+ case $label in
+ REF=cc-armv6
+ REFERENCE_REFS=+refs/heads/master:refs/remotes/reference/master
+ REFERENCE_REFS='+refs/heads/master:refs/remotes/reference/master +refs/heads/v4.x-staging:refs/remotes/reference/v4.x-staging'
+ REFERENCE_REFS='+refs/heads/master:refs/remotes/reference/master +refs/heads/v4.x-staging:refs/remotes/reference/v4.x-staging +refs/heads/v6.x-staging:refs/remotes/reference/v6.x-staging'
+ REFERENCE_REFS='+refs/heads/master:refs/remotes/reference/master +refs/heads/v4.x-staging:refs/remotes/reference/v4.x-staging +refs/heads/v6.x-staging:refs/remotes/reference/v6.x-staging +refs/heads/v7.x-staging:refs/remotes/reference/v7.x-staging'
+ REFERENCE_REFS='+refs/heads/master:refs/remotes/reference/master +refs/heads/v4.x-staging:refs/remotes/reference/v4.x-staging +refs/heads/v6.x-staging:refs/remotes/reference/v6.x-staging +refs/heads/v7.x-staging:refs/remotes/reference/v7.x-staging +refs/heads/v8.x-staging:refs/remotes/reference/v8.x-staging'
+ ORIGIN_REFS=+refs/heads/master:refs/remotes/origin/master
+ ORIGIN_REFS='+refs/heads/master:refs/remotes/origin/master +refs/heads/v4.x-staging:refs/remotes/origin/v4.x-staging'
+ ORIGIN_REFS='+refs/heads/master:refs/remotes/origin/master +refs/heads/v4.x-staging:refs/remotes/origin/v4.x-staging +refs/heads/v6.x-staging:refs/remotes/origin/v6.x-staging'
+ ORIGIN_REFS='+refs/heads/master:refs/remotes/origin/master +refs/heads/v4.x-staging:refs/remotes/origin/v4.x-staging +refs/heads/v6.x-staging:refs/remotes/origin/v6.x-staging +refs/heads/v7.x-staging:refs/remotes/origin/v7.x-staging'
+ ORIGIN_REFS='+refs/heads/master:refs/remotes/origin/master +refs/heads/v4.x-staging:refs/remotes/origin/v4.x-staging +refs/heads/v6.x-staging:refs/remotes/origin/v6.x-staging +refs/heads/v7.x-staging:refs/remotes/origin/v7.x-staging +refs/heads/v8.x-staging:refs/remotes/origin/v8.x-staging'
+ git --version
git version 2.15.0
+ git init
Reinitialized existing Git repository in /home/iojs/build/workspace/node-test-binary-arm/.git/
+ git fetch --no-tags file:///home/iojs/.ccache/node.shared.reference +refs/heads/master:refs/remotes/reference/master +refs/heads/v4.x-staging:refs/remotes/reference/v4.x-staging +refs/heads/v6.x-staging:refs/remotes/reference/v6.x-staging +refs/heads/v7.x-staging:refs/remotes/reference/v7.x-staging +refs/heads/v8.x-staging:refs/remotes/reference/v8.x-staging
fatal: Couldn't find remote ref refs/heads/v7.x-staging
fatal: The remote end hung up unexpectedly

real	0m12.989s
user	0m0.100s
sys	0m0.110s
+ echo 'Problem fetching the shared reference repo.'
Problem fetching the shared reference repo.
+ git fetch --no-tags file:///home/iojs/.ccache/node.shared.reference +refs/heads/jenkins-node-test-commit-arm-fanned-12407-binary-pi1p/cc-armv6:refs/remotes/jenkins_tmp
From file:///home/iojs/.ccache/node.shared.reference
 + a56e581d46...053cb79611 jenkins-node-test-commit-arm-fanned-12407-binary-pi1p/cc-armv6 -> jenkins_tmp  (forced update)

real	0m45.779s
user	0m14.770s
sys	0m5.160s
+ rm -f ****
+ git checkout -f refs/remotes/jenkins_tmp
Warning: you are leaving 60 commits behind, not connected to
any of your branches:

  a56e581d46 added binaries
  da7b4a9d16 test: use tmpDir in test-fs-utimes
  71e7366c2a build: add missing options to help message
  e04d23c1fd test: improve assert messages in napi exception test
 ... and 56 more.

If you want to keep them by creating a new branch, this may be a good time
to do so with:

 git branch <new-branch-name> a56e581d46

HEAD is now at 053cb79611... added binaries

real	7m54.467s
user	0m19.460s
sys	1m0.390s
+ git reset --hard
HEAD is now at 053cb79611 added binaries

real	0m35.108s
user	0m2.750s
sys	0m11.370s
+ git clean -fdx
warning: failed to remove out/Release/.nfs00000000002bfbf000000113: Device or resource busy
Build step 'Execute shell' marked build as failure
TAP Reports Processing: START
Looking for TAP results report in workspace using pattern: *.tap
Did not find any matching files. Setting build result to FAILURE.
Checking ^not ok
Jenkins Text Finder: File set '*.tap' is empty
Notifying upstream projects of job completion
Finished: FAILURE