mirror of
https://github.com/zhw2590582/ArtPlayer.git
synced 2026-10-08 19:06:15 -08:00
test(chapter): [PKG-CHAPTER-05] correlate current-major restart timing failure
This commit is contained in:
1 parent
6d7900df95
commit
dba354f8cd
6 files changed
+2583
-4
No files matched your search
File diff suppressed because it is too large.
Load diff
@@ -0,0 +1,38 @@
|
||||
# PKG-CHAPTER-05 current-major restart timing
|
||||
|
||||
The registered core 6.0.0 and Chapter 2.0.0 candidates were checked with the
|
||||
unchanged installed quality-switch matrix: four old/new combinations across
|
||||
Chromium, Firefox and Windows WebKit, two workers, no retries. The run passed
|
||||
11 cases and failed one in 39,777.596 ms. The failed case used candidate core
|
||||
with published Chapter on WebKit 26.6. Both archives and the exact installed
|
||||
map are recorded in [the evidence](../baselines/chapter-major-timing-validation.json).
|
||||
|
||||
This failure now has a directly correlated event/trace observation. Quality
|
||||
selection was recorded at page time 2982 ms and the required restart at 3601
|
||||
ms, a delay of 619 ms. The first poll returned an empty event list at 3567 ms.
|
||||
The next browser evaluation, trace call `call@241`, took 9989.901 ms and returned
|
||||
the correct restart list at page time 13643 ms. By then the existing 7000 ms
|
||||
poll deadline had expired. Later state showed the requested URL, paused video,
|
||||
position 3.0123779 seconds and no media error.
|
||||
|
||||
Thus this particular failure is not evidence that restart itself was emitted
|
||||
late or missing. It demonstrates that observation through the browser crossed
|
||||
the deadline while the event was already recorded. The trace does not identify
|
||||
whether the underlying delay is media, rendering, OS scheduling or automation;
|
||||
the prior native-video five-second gaps remain relevant but do not prove a
|
||||
single common cause. No production workaround or altered wait policy is justified
|
||||
by this result alone.
|
||||
|
||||
The full report, screenshot, trace and inline attachments were archived before
|
||||
another browser run. The committed record keeps relevant per-case states and
|
||||
the slow trace call; its report hash retains access to the full manifest and
|
||||
other attachments without duplicating them in every case. Historical published
|
||||
core WebKit position-reset assertions remain unchanged and are not counted as
|
||||
new restoration fixes.
|
||||
|
||||
No source, test behavior, timeout, dependency or public API changed. The risk
|
||||
CHAPTER-TIMING-01 stays open and PKG-CHAPTER-05 stays doing. Required real devices
|
||||
and other combinations remain outstanding. Future diagnosis should target the
|
||||
observed browser stall rather than adding an artificial restart delay or rerunning
|
||||
until green. The registered build inputs remain valid because only evidence and
|
||||
status documentation changed. No formal review or remote operation occurred.
|
||||
+1
-1
@@ -572,7 +572,7 @@
|
||||
- PKG-CHAPTER-02: [记录](changes/2026-09-10-PKG-CHAPTER-02-tests.md) [记录](baselines/chapter-validation.json)
|
||||
- PKG-CHAPTER-03: [记录](changes/2026-09-10-PKG-CHAPTER-03-typescript-modules.md) [记录](baselines/chapter-migration-validation.json)
|
||||
- PKG-CHAPTER-04: [记录](changes/2026-09-10-PKG-CHAPTER-04-public-types.md) [记录](baselines/chapter-types-validation.json)
|
||||
- PKG-CHAPTER-05: [记录](changes/2026-09-12-PKG-CHAPTER-05-combinations.md) [记录](baselines/chapter-combinations-checkpoint.json) [记录](changes/2026-09-14-PKG-CHAPTER-05-timing.md) [记录](baselines/chapter-timing-observations.json) [记录](changes/2026-09-15-PKG-CHAPTER-05-native-timing.md) [记录](baselines/chapter-native-timing-validation.json)
|
||||
- PKG-CHAPTER-05: [记录](changes/2026-09-12-PKG-CHAPTER-05-combinations.md) [记录](baselines/chapter-combinations-checkpoint.json) [记录](changes/2026-09-14-PKG-CHAPTER-05-timing.md) [记录](baselines/chapter-timing-observations.json) [记录](changes/2026-09-15-PKG-CHAPTER-05-native-timing.md) [记录](baselines/chapter-native-timing-validation.json) [记录](changes/2026-09-16-PKG-CHAPTER-05-major-timing.md) [记录](baselines/chapter-major-timing-validation.json)
|
||||
- PKG-AMBILIGHT-01: [记录](changes/2026-09-12-PKG-AMBILIGHT-01-contract.md) [记录](baselines/ambilight-contract.md) [记录](baselines/ambilight-release.json) [记录](baselines/ambilight-contract-validation.json)
|
||||
- PKG-AMBILIGHT-02: [记录](changes/2026-09-12-PKG-AMBILIGHT-02-tests.md) [记录](baselines/ambilight-behavior-validation.json) [记录](ambilight-validation.md)
|
||||
- PKG-AMBILIGHT-03: [记录](changes/2026-09-12-PKG-AMBILIGHT-03-lifecycle.md) [记录](ambilight-validation.md) [记录](baselines/ambilight-lifecycle-validation.json)
|
||||
|
||||
@@ -1,5 +1,15 @@
|
||||
# 进度与证据
|
||||
|
||||
## PKG-CHAPTER-05 当前major的时序失败仍可复现
|
||||
|
||||
实际登记候选的清晰度切换矩阵11通过、1个Windows WebKit失败;失败组合为新核心+
|
||||
旧Chapter。本次关联事件与trace,确认restart在选择后619ms记录,后续读取却用时
|
||||
9989.901ms并返回正确列表,超过原7000ms等待窗口。原因尚不能定位到具体子系统,
|
||||
未修改核心、测试等待或重试策略。见[记录](changes/2026-09-16-PKG-CHAPTER-05-major-timing.md)
|
||||
与[证据](baselines/chapter-major-timing-validation.json)。风险继续open、05继续doing,
|
||||
候选build指纹仍有效。接下来推进其他可独立实施的文档/集成任务,不重复跑到绿灯。
|
||||
|
||||
|
||||
## REL-02 登记21库实际候选与构建证据
|
||||
|
||||
基于1b8188834重建并登记21库目标major tarball;校验1918个库输入、1041个构建
|
||||
|
||||
+4
-2
@@ -3053,11 +3053,13 @@
|
||||
"refactor/changes/2026-09-15-PKG-CHAPTER-05-native-timing.md",
|
||||
"refactor/baselines/chapter-native-timing-validation.json",
|
||||
"refactor/changes/2026-09-15-CI-01-installed-webkit.md",
|
||||
"refactor/baselines/ci-installed-webkit-validation.json"
|
||||
"refactor/baselines/ci-installed-webkit-validation.json",
|
||||
"refactor/changes/2026-09-16-PKG-CHAPTER-05-major-timing.md",
|
||||
"refactor/baselines/chapter-major-timing-validation.json"
|
||||
],
|
||||
"compatibleResolution": "记录原生事件和绝对/相对时序,进一步区分媒体驱动耗时、夹具和核心源操作;未证明原因前不改核心、不扩大超时或重复到绿灯。",
|
||||
"closureCriteria": "确认先前超时的来源并有对应可靠回归;后续单次通过不足以关闭。",
|
||||
"workspaceState": "Six-package installed run: WebKit candidate/core Chapter failed after restart while waiting for non-seeking readyState>=2. A trace evaluation took 9939.104 ms and returned false; initial seeked had already fired, followed later by another seeking/canplay. This is a different observed phase from the previous restart timeout; common root cause remains unconfirmed. Keep both failures and investigate without relaxing timeouts. Fixed diagnostic runs with/without trace each retain one WebKit combination failure, while observed native getters/setters remain <=2 ms and page heartbeats show roughly five-second gaps. A no-ArtPlayer native video control restores with one correction yet reproduces a similar five-second gap; deferring correction still shows 5104 ms. Exact cause and relation to each earlier ten-second failure remain unconfirmed; no production timer workaround adopted."
|
||||
"workspaceState": "Six-package installed run: WebKit candidate/core Chapter failed after restart while waiting for non-seeking readyState>=2. A trace evaluation took 9939.104 ms and returned false; initial seeked had already fired, followed later by another seeking/canplay. This is a different observed phase from the previous restart timeout; common root cause remains unconfirmed. Keep both failures and investigate without relaxing timeouts. Fixed diagnostic runs with/without trace each retain one WebKit combination failure, while observed native getters/setters remain <=2 ms and page heartbeats show roughly five-second gaps. A no-ArtPlayer native video control restores with one correction yet reproduces a similar five-second gap; deferring correction still shows 5104 ms. Exact cause and relation to each earlier ten-second failure remain unconfirmed; no production timer workaround adopted. Current major core6/Chapter2 installed matrix: 11 pass, 1 WebKit failure (candidate core + published Chapter). Restart was recorded 619ms after selection; the next trace evaluation took 9989.901ms and returned the correct restart list after the 7000ms observation deadline. This case establishes timely event emission but not the underlying stall cause; no timeout or production workaround adopted."
|
||||
},
|
||||
{
|
||||
"id": "DASH-SDK-01",
|
||||
|
||||
+3
-1
@@ -1489,7 +1489,9 @@
|
||||
"changes/2026-09-14-PKG-CHAPTER-05-timing.md",
|
||||
"baselines/chapter-timing-observations.json",
|
||||
"changes/2026-09-15-PKG-CHAPTER-05-native-timing.md",
|
||||
"baselines/chapter-native-timing-validation.json"
|
||||
"baselines/chapter-native-timing-validation.json",
|
||||
"changes/2026-09-16-PKG-CHAPTER-05-major-timing.md",
|
||||
"baselines/chapter-major-timing-validation.json"
|
||||
]
|
||||
},
|
||||
{
|
||||
|
||||
Reference in new issue
Block a user