V8 CI failing on x64
Open
Nobody has claimed this yet.
incident
platform:linux-intel
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
Consistently failing since https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7350/console yesterday morning.
10:36:47 + PATH=/home/iojs/build/workspace/node-test-commit-v8-linux/deps/v8/depot_tools:/home/iojs/build/workspace/node-test-commit-v8-linux/depot_tools:/home/iojs/venv/bin:/home/iojs/nghttp2/src:/home/iojs/wrk:/usr/lib/ccache:/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ninja -C out.gn/x64.release/ -j 14 d8 cctest inspector-test
10:36:47 python3_bin_reldir.txt not found. need to initialize depot_tools by
10:36:47 running gclient, update_depot_tools or ensure_bootstrap.
10:36:49 make: *** [Makefile:319: v8] Error 1
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 V8 target around Makefile:319 and the failing node-test-commit-v8-linux console logs, especially the ninja command and python3_bin_reldir.txt error. Trace how depot_tools is initialized in this CI job. Done means the x64 V8 CI job completes its d8, cctest, and inspector-test build steps successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100