Node.js v22 RELEASE-CI for armv7 is too slow
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
The cross compilation for armv7 takes more than 9 hours, this makes planning for a release very hard and goes way beyond a person working hours.
https://ci-release.nodejs.org/job/iojs+release/11774/nodes=cross-compiler-rhel8-armv7-gcc-10-glibc-2.28/
Yes, this release has invalidated the cache because of v8 cherry-pick, but still I think it's too much.
I was wondering if we can allocate more resources to the release CI to speed up this process
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 RELEASE-CI job for the armv7 cross-compiler and compare its runtime with the cache-invalidated release context described in the issue. Investigate the available CI resources and identify whether a concrete resource change can reduce the build time; done means a documented bottleneck and a validated improvement plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, infrastructure, performance, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100