test(ci): [CI-01] record complete Chromium source regression

This commit is contained in:
Harvey Zhao committed 2026-09-14 19:31:39 +08:00
1 parent fc566f14d5
commit 442e1dcc96
7 files changed
+1446 -3

No files matched your search

File diff suppressed because it is too large. Load diff
@@ -0,0 +1,36 @@
# CI-01 Chromium 完整源码范围回归
固定源码 HEAD fc566f14d50ac19cfe02f5f0375a168699a91c99、Node24.21.0、
Yarn1.22.22,在Windows执行 `yarn test:browser:source --project=chromium --workers=2`。
没有文件/grep过滤,没有重试,也没有设置诊断SDK或其他ARTPLAYER环境覆盖。
source入口清除安装map;执行期间未修改工作区源码或测试文件。
## 实际结果
152文件、1481项:1480通过、1失败、0跳过、0重试,Playwright耗时839.637秒。
浏览器Chromium153.0.8010.12。子进程和Yarn最终退出码均为1;这不是完整CI通过。
报告、截图和trace归档在 ci-source-chromium-full-report,机器证据记录逐文件
计数、失败断言、附件摘要与实际入口:[ci-source-chromium-validation.json](../baselines/ci-source-chromium-validation.json)。
唯一失败是 dash-sdk.spec.js 中 dash.js4.5.2 的原生对照,不创建ArtPlayer。
完成切轨、稳定暂停、seek=6后,媒体时间一直为6,未达到>6.2;7秒条件等待超时。
这与已定位的DASH-SEEK-01一致:旧SDK空裁剪分支不刷新缓冲量,调度继续使用
暂停前缓存值。此次没有运行诊断补丁、合成timeupdate或改变seek目标。5.2.1
原生对照与其余37项DASH SDK用例通过,但不能据此关闭4.5.2的问题。
风险保留open,并增加本次独立全量运行的证据。没有为了让CI通过而跳过、标成
预期失败、放宽超时或重跑覆盖原始失败。修复/兼容处置继续归PKG-DASH-05。
## 结果解释与后续
source范围保留旧版本、受控错误/能力分支和明确的已有分发产物测试。通过计数
不是1480项新运行时功能,也不是全部原生能力通过。机器证据中的11条含
unsupported的outcome是MediaBunny受控不支持轨道及历史HLS对照,不能解读为
Chromium缺失了11项能力。具体测试中的旧缺陷观察保持原断言。
尚未在本轮执行Firefox/WebKit完整源码范围、Actions系统矩阵或物理设备;
五包installed完整回归属于另一份报告。默认读取工作区dist的原生测试仍需在
后续CI输入审查中核对其构建来源,不能把source入口名称当作全部依赖都现场构建。
CI-01仍doing,整体任务计数不变。下一步优先处理DASH的兼容处置与源码测试的
候选输入来源,并继续其他引擎的完整回归。没有生产代码/依赖修改、push或发布。
+1 -1
View File
@@ -500,7 +500,7 @@
- ENG-09: [记录](changes/2026-09-12-ENG-09-integration.md) [记录](baselines/engineering-integration.json)
- ENG-10: [记录](changes/2026-09-10-ENG-10-test-reliability.md) [记录](test-reliability.md)
- ENG-11: [记录](build-analysis.md) [记录](baselines/bundle-attribution.json) [记录](changes/2026-09-11-ENG-11-build-analysis.md)
- CI-01: [记录](ci-setup.md) [记录](changes/2026-09-13-CI-01-matrix-summary.md) [记录](baselines/ci-matrix-validation.json) [记录](changes/2026-09-13-CI-01-node-consumers.md) [记录](baselines/node-consumer-validation.json) [记录](changes/2026-09-14-CI-01-installed-full.md) [记录](baselines/ci-installed-full-validation.json)
- CI-01: [记录](ci-setup.md) [记录](changes/2026-09-13-CI-01-matrix-summary.md) [记录](baselines/ci-matrix-validation.json) [记录](changes/2026-09-13-CI-01-node-consumers.md) [记录](baselines/node-consumer-validation.json) [记录](changes/2026-09-14-CI-01-installed-full.md) [记录](baselines/ci-installed-full-validation.json) [记录](changes/2026-09-14-CI-01-source-chromium.md) [记录](baselines/ci-source-chromium-validation.json)
- CI-02: [记录](changes/2026-09-14-CI-02-pages-artifact.md) [记录](baselines/pages-artifact-validation.json) [记录](pages-deployment.md)
- PILOT-01: [记录](changes/2026-09-10-PILOT-01-chapter.md) [记录](baselines/pilot-validation.json)
- CORE-01: [记录](changes/2026-09-10-CORE-01-typed-utils.md) [记录](baselines/core-utils-validation.json)
+12
View File
@@ -1,5 +1,17 @@
# 进度与证据
## CI-01 Chromium 完整源码范围回归检查点
固定fc566f14d源码、Node24.21.0/Yarn1.22.22,完整152文件1481项,双worker运行
839.637秒:1480通过、1失败、0跳过/重试,最终退出1。唯一失败为dash.js4.5.2
不接ArtPlayer的原生对照,在稳定暂停seek=6后停滞;与DASH-SEEK-01根因一致,
补充复现证据但风险仍open。没有诊断补丁/合成事件/改变目标或覆盖原始失败。
见[变更](changes/2026-09-14-CI-01-source-chromium.md)和
[证据](baselines/ci-source-chromium-validation.json)。source包含历史/受控/已有
产物对照,不把通过总数当原生能力总数。其他引擎完整source、远端Actions、
设备仍未验收;下一步继续DASH兼容处置及候选输入来源审查。259项状态不变:
190 done、20 doing、49 todo。没有生产代码/依赖修改、push、部署或发布。
## CI-01 五包安装范围完整回归检查点
HEAD 37ebb7a03 上执行无文件/项目过滤的 installed suite,双worker三引擎,
+3 -1
View File
@@ -3063,7 +3063,9 @@
"refactor/changes/2026-09-12-PKG-DASH-05-sdk-checkpoint.md",
"refactor/changes/2026-09-12-PKG-DASH-05-seek-diagnosis.md",
"refactor/baselines/dash-seek-diagnosis.json",
"test/browser/dash-buffer-observer.js"
"test/browser/dash-buffer-observer.js",
"refactor/changes/2026-09-14-CI-01-source-chromium.md",
"refactor/baselines/ci-source-chromium-validation.json"
],
"compatibleResolution": "已用原生 SDK、SourceBuffer/调度指标和 SDK 5 空裁剪刷新的一行诊断回植确认根因。兼容处置尚未落地;不在核心伪造 timeupdate、不偏移 seek、不强制所有旧用户升级 SDK,也不将诊断补丁计为正式上游通过。",
"closureCriteria": "原失败的新旧核心/插件组合有确定根因与对应修复/可验证环境边界;原生对照及原顺序、原目标回归成立,后续偶然通过不能关闭。"
+3 -1
View File
@@ -760,7 +760,9 @@
"changes/2026-09-13-CI-01-node-consumers.md",
"baselines/node-consumer-validation.json",
"changes/2026-09-14-CI-01-installed-full.md",
"baselines/ci-installed-full-validation.json"
"baselines/ci-installed-full-validation.json",
"changes/2026-09-14-CI-01-source-chromium.md",
"baselines/ci-source-chromium-validation.json"
]
},
{
+7
View File
@@ -5,6 +5,13 @@ three-engine configuration. The launcher clears only ARTPLAYER_BROWSER_ARTIFACTS
from the child environment, so an installed-core map inherited from CI cannot
mislabel source/explicit-vendor SDK tests. The caller's environment is untouched.
Other deliberate fixture switches retain their existing meaning.
The complete Chromium source collection at the recorded checkpoint executed
1,481 cases in 152 files: 1,480 passed and the original dash.js 4.5.2 native seek
control failed with exit 1. See
`../../refactor/baselines/ci-source-chromium-validation.json`; this is evidence of
the open DASH-SEEK-01 issue, not a green full CI or all-engine result. Source scope
also retains explicit historical and committed-artifact cases; its name does not
promise that every dependency is rebuilt from current source in every test.
`yarn test:browser:installed` requires ARTPLAYER_BROWSER_ARTIFACTS from
`yarn test:package --include=artplayer-plugin-ambilight,artplayer-proxy-canvas,artplayer-plugin-document-pip`.