Depot runners lost mid-job evicted 2 merge-queue entries in 27h
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 18/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions
- 领域
- ci-cd
调研方向
Start with the two merge_group runs listed in the issue and check the Depot dashboard for instance terminations or OOM kills at the reported times. The issue says the cause is outside this repository; done means identifying whether runner termination or memory pressure explains the failures and, if the problem recurs, evaluating larger e2e runners or a Depot support ticket.
由索引模型根据 Issue 内容生成。
描述
Two merge-queue entries were evicted in about 27 hours because a Depot runner (depot-ubuntu-24.04-4) stopped reporting partway through a job. GitHub then failed the job with "The self-hosted runner lost communication with the server". Both jobs normally finish in 1–5 minutes on the same label. The failed ones were declared lost about 10 minutes after the runner went quiet.
| When (UTC) | merge_group run | Job | Runner | Normal duration | Failed after |
|---|---|---|---|---|---|
| 2026-10-20 16:48 | 39460266425 (PR #1617) | e2e (ubuntu-latest, e2e_vex_build, pipenv) | depot-wkpbh4r80h | ~1 min | 10m00s |
| 2026-10-21 19:02 | 39657631762 (PR #1593) | e2e (ubuntu-latest, e2e_gradle_discovery_build …) | depot-v42fm5z0wd | ~5 min | 15m35s |
Both PRs merged after a rebuild, so each loss cost one full queue cycle (about 10 minutes plus the rebuild of every entry behind them). Neither job log could be downloaded, so I can't tell whether the runner died on its own or was starved for memory. The Gradle leg is the heaviest Linux e2e leg. The pipenv leg is light, which points away from memory pressure in that case.
This repo can't fix the cause; it's runner infrastructure. Next steps for a maintainer:
- Check the Depot dashboard for instance terminations or OOM kills at those times.
- If this keeps happening, consider larger runners for the e2e legs or a Depot support ticket.
The CI janitor will add new occurrences here.
Generated by Claude Code
- 主要语言
- Rust
- 星标
- 8
- 派生
- 1
- 平均合并
- 19 小时 9 分钟
- 30 天内合并 PR
- 641
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
SocketDev/socket-patch 的其他 Issue
-
agent:triaged bug bughunt pm:npm priority:p3 ux
难度 2/5 1-3 小时 新手友好度 75/100
SocketDev/socket-patch#1072 · 2 条评论 ·
维护者通常 1 天内回复
-
agent:needs-human agent:triaged ci-perf priority:p3
难度 3/5 1-2 天 新手友好度 45/100
SocketDev/socket-patch#1720 · 4 条评论 ·
维护者通常 1 天内回复
-
Nightly Windows test shards fail on temp-path spelling (RUNNER~1 vs canonical \\?\ paths)可能已有人在做 @mikolalysenko 于 2 天前认领。 未关闭agent:claimed agent:triaged ci-janitor priority:p3
难度 4/5 3-5 天 新手友好度 55/100
SocketDev/socket-patch#1689 · 6 条评论 ·
维护者通常 1 天内回复
-
agent:needs-human agent:triaged ci-perf priority:p3
难度 2/5 1-3 小时 新手友好度 48/100
SocketDev/socket-patch#1670 · 2 条评论 ·
维护者通常 1 天内回复
-
agent:triaged ci-janitor priority:p3
难度 3/5 1-2 天 新手友好度 55/100
SocketDev/socket-patch#1665 · 3 条评论 ·
维护者通常 1 天内回复
查看 SocketDev/socket-patch 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 61/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
rust-embedded/heapless#694 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
farion1231/cc-switch#8899 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
manuscript-lang/manuscript#1364 ·
维护者通常 1 天内回复