Evidence tutorials CI: issuer-backed dev start intermittently fails before readiness and its startup logs are lost
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
从 crates/registry-evidencectl/tests/dev_lifecycle.rs 和 “Evidence tutorials from source” 作业入手。检查测试如何处理 dev start 失败，以及 failed-start 日志保存在何处；检查作业使用的输出限制和脱敏方式。完成的标准是：发生失败时，能够显示有长度限制且经过脱敏的启动日志，或将其作为构件上传，以便诊断下一次间歇性故障。
由索引模型根据 Issue 内容生成。
描述
real_issuer_lifecycle_issues_typed_service_claims_and_stops_cleanly (crates/registry-evidencectl/tests/dev_lifecycle.rs, run by the "Evidence tutorials from source" job) failed once in a merge-group run after about 6 seconds:
issuer-backed dev start failed
error[evidence.dev.start-failed] local development session logs: The local Evidence services failed before reaching readiness.
next: Inspect the preserved startup logs at .../target/debug/evidence-native-lifecycle-*/tutorial/.evidence/failed-start, ...
Failing run: https://github.com/registrystack/registry-stack/actions/runs/39132836323
The same tree passed this job in the pull request's own CI run and passed three of three local runs under Docker, so the failure is nondeterministic and not caused by that change.
The cause cannot be recovered: dev start preserves its startup logs under target/, which dies with the runner, and the test's panic message prints only dev start's stdout and stderr.
Two asks:
- When
dev startfails, have the test print the preservedfailed-startlogs, bounded and redacted like the rest of the job output. Alternatively, have the job upload that directory as an artifactif: failure(). The next occurrence then names its own cause. - A candidate cause to check once logs exist:
unused_port_pair()binds two ephemeral ports and drops them beforedev starthands them to Evidence and to the issuer container, so another process on the runner can take one in between. #1870 is the same class of port collision on the BReg tutorial gate.
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- 平均合并
- 9 小时 24 分钟
- 30 天内合并 PR
- 271
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
registrystack/registry-stack 的其他 Issue
-
area:docs documentation
难度 2/5 1-3 小时 新手友好度 76/100
registrystack/registry-stack#2253 ·
维护者通常 1 天内回复
-
area:coordinator bug
难度 2/5 1-3 小时 新手友好度 82/100
registrystack/registry-stack#2252 ·
维护者通常 1 天内回复
-
area:release bug
难度 2/5 1-3 小时 新手友好度 74/100
registrystack/registry-stack#2248 ·
维护者通常 1 天内回复
-
area:breg documentation
难度 1/5 1-3 小时 新手友好度 88/100
registrystack/registry-stack#2233 ·
维护者通常 1 天内回复
-
area:breg bug
难度 2/5 1-3 小时 新手友好度 90/100
registrystack/registry-stack#2231 ·
维护者通常 1 天内回复
查看 registrystack/registry-stack 的全部 Issue
相似的 Issue
-
documentation priority:p2 type:chore
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
-
dispatch:sol-high documentation
难度 1/5 1-3 小时 新手友好度 85/100
carrick-sh/carrick#768 · 1 条评论 ·
维护者通常 1 天内回复
-
correctness postgres tursopg
难度 2/5 1-3 小时 新手友好度 76/100
tursodatabase/turso#10442 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
ankitects/anki#5864 · 1 个 reaction ·
维护者通常 2 天内回复
-
area: config effort: S good first issue P3 type: bug
难度 2/5 1-3 小时 新手友好度 70/100
ferenyl/azuredevopstui#63 ·