node-test-binary-armv7l initialize repo fail

[F3n67u]

Console Output

00:21:55 + git init
00:21:55 Reinitialized existing Git repository in /home/iojs/build/workspace/node-test-binary-armv7l/.git/
00:21:55 + git fetch --no-tags file:///home/iojs/.ccache/node.shared.reference +refs/heads/jenkins-node-test-commit-arm-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-binary-pi1p/cc-armv7:refs/remotes/jenkins_tmp
00:21:55 fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
00:21:55 fatal: Could not read from remote repository.
00:21:55 
00:21:55 Please make sure you have the correct access rights
00:21:55 and the repository exists.
00:21:55 
00:21:55 real	0m0.033s
00:21:55 user	0m0.013s
00:21:55 sys	0m0.018s
00:21:55 + echo Could not fetch refs/heads/jenkins-node-test-commit-arm-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-binary-pi1p/cc-armv7 from the local reference repo, trying the temp repo directly.
00:21:55 Could not fetch refs/heads/jenkins-node-test-commit-arm-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-binary-pi1p/cc-armv7 from the local reference repo, trying the temp repo directly.
00:21:55 + grep -q '^147.75.66.203' /home/iojs/.ssh/known_hosts
00:21:55 + ssh-agent sh -c 'ssh-add **** && git fetch --no-tags binary_tmp@147.75.66.203:binary_tmp.git +refs/heads/jenkins-node-test-commit-arm-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-binary-pi1p/cc-armv7:refs/remotes/jenkins_tmp'
00:21:55 Identity added: **** (****)
00:21:57 fatal: Couldn't find remote ref refs/heads/jenkins-node-test-commit-arm-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-binary-pi1p/cc-armv7
00:21:57 
00:21:57 real	0m1.245s
00:21:57 user	0m0.045s
00:21:57 sys	0m0.029s
00:21:57 fatal: The remote end hung up unexpectedly
00:21:57 Build step 'Execute shell' marked build as failure

Build link

https://ci.nodejs.org/job/node-test-binary-armv7l/1572/RUN_SUBSET=native,label=debian10-armv7l/console
https://ci.nodejs.org/job/node-test-binary-armv7l/1572/RUN_SUBSET=js,label=debian10-armv7l/console

Related pr

nodejs/node#43903 (comment)

[richardlau]

The '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository errors are expected (this is reference repository that doesn't exist). The build then tries to access the binary temp repository directly:

echo Could not fetch refs/heads/jenkins-node-test-commit-arm-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-binary-pi1p/cc-armv7 from the local reference repo, trying the temp repo directly.

and has failed to find the corresponding branch

00:21:57 fatal: Couldn't find remote ref refs/heads/jenkins-node-test-commit-arm-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-binary-pi1p/cc-armv7
00:21:57 

Branches in the binary temp repo are only expected to exist for a maximum of 7 days -- there's a cron on the machine that runs https://github.com/nodejs/build/blob/main/ansible/roles/jenkins-workspace/files/clean_binary_tmp.sh at 5am every day. However I don't see the jenkins-node-test-commit-arm-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-binary-pi1p branch in the log file of deleted branches so I don't think the branch has been deleted by the script. Strangely if I search for branches for the commit (45e01b132a69386d0cf9dae57985ba293e6e016a) then the Windows fanned branch still exists but not the arm-fanned ones 😕:

# sudo -u binary_tmp git branch | sed /\*/d | grep 45e01b132a69386d0cf9dae57985ba293e6e0
16a
  jenkins-node-test-commit-windows-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a
  jenkins-node-test-commit-windows-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-bin-win-vs2019
  jenkins-node-test-commit-windows-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-bin-win-vs2019-arm64
  jenkins-node-test-commit-windows-fanned-45e01b132a69386d0cf9dae57985ba293e6e016a-bin-win-vs2019-x86
#

[F3n67u]

Another failure: https://ci.nodejs.org/job/node-test-binary-armv7l/1650/RUN_SUBSET=native,label=debian10-armv7l/console

@richardlau could you help take a look at this cause to see if there is some similar pattern? I don't have access to the Jenkins machine so I am sorry that I could not help.

[richardlau]

Another failure: https://ci.nodejs.org/job/node-test-binary-armv7l/1650/RUN_SUBSET=native,label=debian10-armv7l/console

@richardlau could you help take a look at this cause to see if there is some similar pattern? I don't have access to the Jenkins machine so I am sorry that I could not help.

For this one, the branch was deleted by the clean up script:

# grep jenkins-node-test-commit-arm-fanned-aad1ed80df7710903eaff5529407036ed1353f6a-binary-pi1p clean_binary_tmp.log
Deleted branch jenkins-node-test-commit-arm-fanned-aad1ed80df7710903eaff5529407036ed1353f6a-binary-pi1p/cc-armv7 (was e31de30fa38a).

The branch was deleted on 8 July (i.e. it was already a week old then):

Fri Jul  8 05:00:01 UTC 2022
41G     /home/binary_tmp/binary_tmp.git/
Deleted branch jenkins-node-test-commit-arm-fanned-350a6a8d59914eaf05b46f1ca1b7c356d4204add-binary-pi1p/cc-armv7 (was 2515164bd3e7).
Deleted branch jenkins-node-test-commit-arm-fanned-aad1ed80df7710903eaff5529407036ed1353f6a-binary-pi1p/cc-armv7 (was e31de30fa38a).

So for this PR it's expected that the resumes are failing.

[github-actions]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.