node-test-binary-armv7l initialize repo fail #3002

Activity

1. richardlau commented on Jul 25, 2022

   

   richardlau

   on Jul 25, 2022

   Member

   More actions

   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
   #

   👍React with 👍1Reacted by Feng Yu
2. F3n67u commented on Jul 26, 2022

   

   F3n67u

   on Jul 26, 2022

   Last edited by F3n67u

   ContributorAuthor

   More actions

   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.
3. richardlau commented on Jul 26, 2022

   

   richardlau

   on Jul 26, 2022

   Last edited by richardlau

   Member

   More actions

   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.
4. github-actions commented on May 23, 2023

   

   github-actionsbot

   on May 23, 2023

   More 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.
5. github-actions

   added

   stale

   on May 23, 2023
6. targos

   closed this as not plannedon May 23, 2023