Repository navigation
diag(shell): 失败转储的结构化解析 (#73) - #286
Merged
Merged
Conversation
One parser turns the dump into mode, stage and per-tab counters so the drained verdict is computed the same way every time.
This was referenced Oct 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
内容
新增
experiments/shell/summarize_failure.py与其测试，把 Workspace 失败转储解析成结构化行：workspace-failure mode=… stage=… what=…与tab <group>:<index> …mode、stage、what、tabs[]describe()给出一行判词：rejected=<n> drained=yes/no child=<exit>为什么
这两周读失败日志的方式一直是人工 grep + 眼算：先找
workspace-failure，再逐行抄input_high_water/output_bytes/consumed，还要自己判断是否output_bytes == consumed。现在一条命令即可得到同样的判读，且判定口径写进代码（
drained只在两者相等时为 yes），避免我在不同轮次里用不同口径读同一份数据。验证
python -m unittest experiments.shell.test_summarize_failure→ 4 tests OK，覆盖：stage与两个标签页的解析；stage）仍可解析；drained与子进程状态判词；边界
Refs #73 #38