Repository navigation
diag(ui): 超时信息带上 CreateProcess→JS 间隔 (#144) - #274
Merged
Merged
Conversation
When the preload checkpoint carries a start time the failure line now also prints how long after CreateProcess Node reached its first JS line.
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.
内容
按 #144 的最新分析（样本 D：
CreateProcess返回后约 8.82 s 才执行到 Node 的第一行 JS），把这段间隔直接算进超时消息：started（即 Node 确实执行到 preload）时才追加该字段；为什么
上一轮的判据是「preload 是否写入」，能区分"完全没进 JS"与"进了但卡住"；但它不能量化"CreateProcess 到 JS 之间"的耗时。样本 D 是靠人工对账
started与截止时刻才得出 8.82 s，本次把它固化进失败信息，下一次命中即可直接读数（不碰 10 秒期限）。验证
python -m unittest research.ui.test_raster_style_reference→ 11 tests OK。边界
started是 Node 侧毫秒时间戳，与父进程time.time()的时钟偏差未校准，差值只作指示。Refs #144