`binary_tmp` directory on test-mnx-ubuntu2204-x64-1 causing space issues and PR test failures
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- git, node.js
- 领域
- devops, infrastructure
调研方向
Start by checking how the binary_tmp repository is created, updated, and cleaned up on the workspace machine, then compare its current size with the earlier 80GB figure. Identify cleanup or retention options that reduce repository growth without breaking PR tests or git_rebase jobs. Done means a practical way to control the repository size is identified and the workspace queues remain healthy.
由索引模型根据 Issue 内容生成。
描述
Today the subject workspace machine hit an out of disk space condition causing PR tests to fail if they were scheduled on that machine and also causing all git_rebase jobs to fail as the binary_tmp repository they use is hosted on this workspace machine.
Previously I'd see the repository run at about 80GB but today it is sitting at just over 125GB in size. This seemingly unbounded increase should be considered unsustainable.
The rest of the iojs workspaces on the machine are now totalling about 270GB which is broadly consistent with the other two workspace machines. I expect that this figure has also increased as the size of the repository has increased over time although we have also places restrictions ont he number of parallel jobs that node-test-commit can run which will have partially mitigated the larger sizes, although it would seem not be enough.
This issue should cover identifying any means by which we can reduce/clean up the size of the binary_tmp repository.
At the time of writing I've cleared up a small amount of space (30GB) but will leave that workspace machine online so it can be dedicated for the binary_tmp repository for now pending a resolution. We should keep an eye on the queues to make sure nothing is blocked/deadlocked by only having two workspace systems available.
- 主要语言
- Jinja
- 星标
- 542
- 派生
- 184
- 平均合并
- 4 天 16 小时
- 30 天内合并 PR
- 12
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nodejs/build 的其他 Issue
-
build-agenda
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 3 天内回复
-
jenkins
难度 3/5 1-2 天 新手友好度 48/100
维护者通常 3 天内回复
-
Request for Alpine Linux availability on `citgm-smoker-nobuild`可能已有人在做 @sxa 于 1 天前认领。 未关闭
nodejs/build#4535 · 2 条评论 · 已指派 1 人 ·
维护者通常 3 天内回复
-
incident
难度 5/5 一周以上 新手友好度 30/100
维护者通常 3 天内回复
相似的 Issue
-
area: client bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
OCIRepository: pick the Helm chart layer automatically when the first layer is a provenance file未关闭
难度 2/5 1-3 小时 新手友好度 78/100
fluxcd/source-controller#2198 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
e2e-failure ready-to-code
难度 1/5 1 小时以内 新手友好度 82/100
redhat-developer/rhdh-plugin-export-overlays#4485 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100