Flaky: Linux owlet sometimes fails on power-loss-truncated corpus hoots (owlet-failed vs incomplete-read)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with readers/hoot.py::_run and the named corpus and backup tests, then inspect how quarantine reasons and owlet output are recorded. Run the Linux owlet repeatedly on the two named truncated hoot files and compare exit status, stderr, and wpilog output. Done when the intermittent failure is characterized and the tests verify a reliable handling strategy for it.
由索引模型根据 Issue 内容生成。
描述
Seen on PR IgniteRobotics/flashpoint-private#15, CI run 37319717473, corpus job attempt 1. The same commit passed on rerun, and passed on two earlier runs.
The GACMP_E10 truncated hoots (GACMP_E10_rio_2026-04-11_19-26-19.hoot, GACMP_E10_6E94…_2026-04-11_19-29-15.hoot) were quarantined as owlet-failed instead of being ingested with incomplete-read. This failed:
tests/test_ingest_corpus.py::test_expected_successes_and_quarantinestest_truncated_hoot_flagged_short_coveragetests/acquire/test_backup_corpus.py::test_restore_drill_reproduces_the_ledger_and_gold. In this one the original lake converted the hoot and the rebuild didn't, all within the same run.
readers/hoot.py::_run treats a non-zero owlet exit as owlet-failed unless the incomplete-read marker appears in stdout or stderr. The Linux owlet appears to be nondeterministic on truncated hoots: it sometimes exits non-zero without the marker. The macOS owlet exits 0 on this file in 20 of 20 runs, so this can't be reproduced locally. The owlet stderr detail isn't in the CI log.
Next steps:
- Log the owlet exit code and the last stderr line in the quarantine reason detail.
- Loop the Linux owlet on these files to characterise the failure.
- Consider a single retry, or accepting a non-zero exit when a non-empty wpilog was written.
🤖 Generated with Claude Code
- 主要语言
- Python
- 星标
- 0
- 派生
- 1
- 平均合并
- 19 小时 40 分钟
- 30 天内合并 PR
- 14
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
IgniteRobotics/flashpoint 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
IgniteRobotics/flashpoint#45 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
IgniteRobotics/flashpoint#44 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
IgniteRobotics/flashpoint#43 ·
维护者通常 1 天内回复
-
bug good first issue
难度 1/5 1 小时以内 新手友好度 85/100
IgniteRobotics/flashpoint#12 ·
维护者通常 1 天内回复
-
tools/update-owlet-manifest.py ignores --help and starts downloading可能重新可做 @yoveneim 于 10 天前认领，目前没有进行中的 PR。 未关闭bug good first issue
难度 2/5 1-3 小时 新手友好度 83/100
IgniteRobotics/flashpoint#11 · 1 条评论 ·
维护者通常 1 天内回复
查看 IgniteRobotics/flashpoint 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
aws/sagemaker-python-sdk#6554 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
huggingface/diffusers#15170 ·
维护者通常 1 天内回复
-
[BUG] LLM conflict check ignores MNEMOSYNE_LLM_MAX_TOKENS, so reasoning models return empty replies未关闭
难度 2/5 1-3 小时 新手友好度 62/100
mnemosyne-oss/mnemosyne#1325 ·
维护者通常 1 天内回复
-
enhancement meshtastic-2.8
难度 2/5 1-3 小时 新手友好度 62/100
pskillen/meshflow-api#459 ·