Repository navigation
Conversation
5c1e9ea to
cdb102c
Compare
e9e4a17 to
60d0c77
Compare
CI Regression ReportSource CI run · source state at render:
Release regression — ✅ HEAD/base failures 0/0; raw binary +0.005232%Package and image size
Startup latency and PSS
Concurrency matrix
Frontend differential — ✅ 1,020/1,020 cases matched; 0 issues
Agent episodes · Moli vs Chromium — ✅ 8/8 Moli episodes passed; 0 failures
Runtime and CDP session contracts — ✅ 26 contract cases; 0 failures
CDP smoke — ✅ 52/52 groups passed; 622 scenariosWorkers: 4 · cumulative group time: 139.29 s · failed groups: 0
WebMainBench · 545 pages — ✅ 545/545 completed; 0 unexpected failures
Frozen HTML · Linux · Diagnostics: All artifact fields are parsed by the trusted default-branch renderer; missing or invalid inputs remain visible as unavailable. |
Sequential Navigation Soak A/B✅ HEAD completed the 200-navigation resilience and memory observation. One browser process, one target, and one CDP session navigate CSDN → SegmentFault → Huaban → example.com repeatedly. This run issued 200 Common ancestor Session resilience
A public-page failure is reported separately from an unrecoverable session. The soak requires all navigation attempts, zero failed recovery, zero lifecycle/network ordering violations, and complete resource evidence. Process-tree memory
HEAD memory by 50-navigation quarter
Raw reports and per-navigation boundary samples: workflow run and full Public-site timing and memory are observational. Use the A/B deltas and trend shape as evidence, not as a deterministic performance threshold. |
Spider Bench A/B✅ All benchmark browser service runs completed; results are informational. Public HEAD: 184 / 240 rows; 38 / 48 sites produced rows; 10 unexpected empty sites. ✅ Deterministic fixture contract is clean. Common ancestor Public 48-site run · informational
Public-site content, timing, and memory are noisy. This single A/B run reports evidence only; site outcome counts explain missing rows without treating them as a deterministic regression. CPU and memory timelinesThese are bounded 40-point views of the same complete process-tree samples used by the HTML report. CPU uses 100% per occupied logical core; memory lines are RSS first and PSS second when complete PSS samples are available. Basexychart-beta
title "Base CPU"
x-axis "Elapsed seconds" [1.036, 1.536, 2.537, 4.039, 5.04, 6.54, 7.542, 9.043, 10.044, 11.544, 12.545, 14.048, 15.05, 16.551, 17.552, 19.054, 20.056, 21.559, 22.561, 24.062, 25.062, 26.565, 27.567, 29.07, 30.071, 31.573, 32.575, 34.078, 35.078, 36.58, 37.582, 38.083, 39.084, 40.086, 41.086, 41.587, 42.588, 44.09]
y-axis "CPU percent" 0 --> 200
line [17.99, 127.9, 123.9, 137.87, 120, 102.04, 149.72, 56.01, 61.97, 110.02, 33.94, 2, 101.87, 69.96, 59.92, 61.93, 105.76, 129.71, 109.83, 131.84, 150.08, 35.93, 107.76, 135.7, 105.93, 85.95, 5.99, 127.8, 101.97, 111.92, 7.98, 0, 27.99, 135.86, 169.82, 13.96, 87.89, 111.92]
xychart-beta
title "Base memory: RSS then PSS"
x-axis "Elapsed seconds" [0.035, 1.036, 1.536, 2.537, 4.039, 5.04, 6.54, 7.542, 9.043, 10.044, 11.544, 12.545, 14.048, 15.05, 16.551, 17.552, 19.054, 20.056, 21.559, 22.561, 24.062, 25.062, 26.565, 27.567, 29.07, 30.071, 31.573, 32.575, 34.078, 35.078, 36.58, 37.582, 38.083, 39.084, 40.086, 41.086, 41.587, 42.588, 44.09, 44.878]
y-axis "Memory MiB" 0 --> 500
line [13.1, 73.02, 97.77, 99.07, 143.88, 156.78, 116.35, 137.09, 126.36, 143.11, 124.86, 136.96, 120.55, 142.96, 115.91, 119.4, 154.31, 131.84, 163.75, 247.87, 187.91, 200.99, 143.55, 162.93, 142.85, 137.05, 146.42, 135.61, 203.24, 229.11, 148.72, 129.26, 129.06, 137.99, 165.2, 155.91, 127.28, 145.46, 162.6, 0]
line [9.89, 69.83, 94.51, 95.72, 140.53, 153.52, 112.92, 134.07, 122.77, 139.68, 121.46, 133.56, 117.13, 139.54, 112.49, 115.98, 150.88, 128.49, 160.43, 244.03, 184.42, 197.5, 140.16, 159.54, 139, 133.41, 143.03, 131.97, 199.54, 224.91, 145.08, 125.62, 125.42, 133.92, 161.59, 152.3, 123.64, 141.82, 156.28, 0]
HEADxychart-beta
title "HEAD CPU"
x-axis "Elapsed seconds" [0.536, 1.037, 2.038, 3.039, 4.041, 4.542, 5.042, 5.542, 6.543, 7.543, 8.545, 9.547, 10.547, 12.05, 13.052, 14.054, 15.056, 16.057, 17.059, 18.06, 19.561, 20.562, 21.563, 22.564, 23.565, 24.565, 25.566, 26.568, 28.069, 29.071, 30.071, 31.073, 32.075, 33.074, 34.076, 35.578, 36.579, 37.579]
y-axis "CPU percent" 0 --> 200
line [4, 17.96, 101.93, 113.83, 137.8, 129.71, 125.9, 129.98, 119.79, 134, 117.76, 129.73, 103.95, 85.84, 113.76, 41.92, 47.93, 147.83, 101.78, 107.93, 101.94, 121.85, 117.88, 125.87, 45.95, 120.21, 117.93, 87.77, 71.98, 59.87, 41.99, 109.77, 83.92, 9.99, 103.76, 161.89, 89.95, 123.93]
xychart-beta
title "HEAD memory: RSS then PSS"
x-axis "Elapsed seconds" [0.036, 0.536, 1.037, 2.038, 3.039, 4.041, 4.542, 5.042, 5.542, 6.543, 7.543, 8.545, 9.547, 10.547, 12.05, 13.052, 14.054, 15.056, 16.057, 17.059, 18.06, 19.561, 20.562, 21.563, 22.564, 23.565, 24.565, 25.566, 26.568, 28.069, 29.071, 30.071, 31.073, 32.075, 33.074, 34.076, 35.578, 36.579, 37.579, 38.189]
y-axis "Memory MiB" 0 --> 500
line [13.12, 54.15, 76.13, 101.87, 123.61, 136.25, 132.79, 148.32, 134.45, 126.29, 133.07, 150.03, 161.35, 143.19, 124.8, 139.21, 114.57, 125.76, 151.85, 132.91, 139.38, 265.9, 185.03, 195.96, 211.98, 135.59, 155, 147.42, 132.49, 146.32, 143.13, 146.05, 193.8, 155.11, 128.07, 155.03, 136.81, 134.14, 151.18, 0]
line [9.74, 50.66, 72.98, 98.36, 120.1, 132.75, 129.39, 144.72, 130.8, 123.12, 129.27, 146.42, 157.77, 139.59, 121.2, 135.61, 110.96, 122.15, 148.29, 129.31, 135.76, 262.3, 181.53, 192.39, 208.39, 131.86, 151.7, 143.85, 128.88, 142.77, 139.53, 142.45, 190.99, 151.5, 124.47, 150.93, 133.1, 130.74, 147.59, 0]
Deterministic fixture · required contractThe fixture exercises 15 routes: 8 are expected to emit rows and 7 intentionally exercise empty, loading, or timeout behavior.
Full HTML, JSON, CSV, logs, and page snapshots: workflow run and full The public-web A/B is informational. The exact HEAD fixture contract runs as a separate required CI check; timing and public-site content deltas remain non-blocking. |
ShadowRoot members and the related slot/text bindings now use native receiver brands through generated declarations. Retain the native owner resolution inside the implementation, and expose the existing onslotchange callbacks through the ShadowRoot declaration.
Regression coverage checks cross-realm genuine receivers, forged/proxy rejection, conversion ordering and live/windowless owner behavior.
Depends on #1861.
Validation on base
cdb102cdc607: cargo fmt --all; cargo clippy --workspace --all-targets --all-features -- -D warnings; cargo nextest run --no-fail-fast. All passed (20,531 passed, 18 existing skips; 32 build jobs and test threads, no automatic retries). Focused regressions also passed.