Process on rhel9-ppc64le was stuck for ~9 hours for a git operation
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
Process on rhel9-ppc64le was stuck for ~9 hours
https://ci.nodejs.org/job/node-test-commit-plinux/64340/nodes=rhel9-ppc64le/
Details
08:27:45 Started by upstream project "[node-test-commit-plinux](https://ci.nodejs.org/job/node-test-commit-plinux/)" build number [64340](https://ci.nodejs.org/job/node-test-commit-plinux/64340)
08:27:45 originally caused by:
08:27:45 Started by upstream project "[node-test-commit](https://ci.nodejs.org/job/node-test-commit/)" build number [88782](https://ci.nodejs.org/job/node-test-commit/88782)
08:27:45 originally caused by:
08:27:45 Started by upstream project "[node-test-pull-request](https://ci.nodejs.org/job/node-test-pull-request/)" build number [74209](https://ci.nodejs.org/job/node-test-pull-request/74209)
08:27:45 originally caused by:
08:27:45 Started by user [Trivikram Kamat](https://ci.nodejs.org/user/trivikr)
08:27:45 Running as SYSTEM
08:27:45 [EnvInject] - Loading node environment variables.
08:27:45 Building remotely on [test-ibm-rhel9-ppc64_le-1](https://ci.nodejs.org/computer/test-ibm-rhel9-ppc64_le-1/) (rhel9-ppc64le) in workspace /home/iojs/build/workspace/node-test-commit-plinux/nodes/rhel9-ppc64le
08:27:45 Running Prebuild steps
08:27:45 [EnvInject] - Injecting environment variables from a build step.
08:27:46 [EnvInject] - Injecting as environment variables the properties content
08:27:46 STATUS_LABEL=node-test-commit-plinux-rhel9-ppc64le
08:27:46
08:27:46 [EnvInject] - Variables injected successfully.
08:27:46 Success build fororg.jenkinsci.plugins.envinject.EnvInjectBuilder@74379f76
08:27:46 The recommended git tool is: NONE
08:27:46 using credential 96d5f81c-e9ad-45f7-ba5d-bc8107c0ae2c
08:27:46 > git rev-parse --resolve-git-dir /home/iojs/build/workspace/node-test-commit-plinux/nodes/rhel9-ppc64le/.git # timeout=10
08:27:46 Fetching changes from the remote Git repository
17:20:03 Build was aborted
17:20:03 Aborted by [Trivikram Kamat](https://ci.nodejs.org/user/trivikr)
I aborted it by clicking on red "X" icon, and also visiting /term in the URL.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Jenkins build 64340 on the rhel9-ppc64le node and inspect the workspace step at git rev-parse --resolve-git-dir, followed by the remote-fetch phase. Determine why the Git operation remained stuck for roughly nine hours and define completion as a reproducible diagnosis plus a verified way to prevent or safely handle the hang.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, linux
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100