Repository navigation
Conversation
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.035, 2.538, 3.538, 4.539, 5.039, 6.04, 7.541, 8.542, 10.043, 11.044, 12.546, 13.547, 15.049, 16.051, 17.552, 18.552, 20.053, 21.057, 22.562, 23.062, 23.563, 24.565, 26.066, 27.068, 28.568, 29.568, 31.07, 32.072, 33.617, 34.62, 36.121, 37.122, 38.625, 39.625, 41.127, 42.128, 43.129, 43.63]
y-axis "CPU percent" 0 --> 200
line [8, 123.78, 129.97, 133.84, 165.97, 139.9, 171.86, 152.09, 137.88, 137.68, 145.91, 135.89, 2, 107.8, 20, 54, 71.92, 123.1, 103.33, 107.9, 103.87, 99.93, 109.99, 131.79, 103.98, 135.92, 83.94, 111.79, 89.85, 129.58, 54.01, 11.97, 99.71, 107.91, 17.97, 131.89, 185.74, 117.8]
xychart-beta
title "Base memory: RSS then PSS"
x-axis "Elapsed seconds" [0.035, 1.035, 2.538, 3.538, 4.539, 5.039, 6.04, 7.541, 8.542, 10.043, 11.044, 12.546, 13.547, 15.049, 16.051, 17.552, 18.552, 20.053, 21.057, 22.562, 23.062, 23.563, 24.565, 26.066, 27.068, 28.568, 29.568, 31.07, 32.072, 33.617, 34.62, 36.121, 37.122, 38.625, 39.625, 41.127, 42.128, 43.129, 43.63, 44.397]
y-axis "Memory MiB" 0 --> 500
line [12.28, 66.66, 118.04, 114.29, 138.58, 158.63, 183.19, 178.46, 181.5, 174.78, 211.73, 173, 160.64, 153.29, 160.29, 145.14, 146.08, 175.18, 166.61, 217.19, 283.96, 238.92, 213.72, 159.63, 159.13, 197.25, 174.49, 162.08, 160.98, 160.79, 164.96, 168.14, 149.57, 160.35, 168.18, 153.66, 181.1, 193.46, 204.05, 0]
line [8.98, 62.97, 114.87, 111.12, 135.37, 154.78, 179.88, 175.12, 178.13, 171.43, 207.96, 169.45, 156.98, 149.66, 156.66, 141.63, 142.59, 171.56, 162.88, 213.53, 280.08, 234.8, 210.12, 155.85, 155.32, 193.46, 169.35, 158.27, 157.17, 156.89, 160.94, 164.22, 145.58, 156.48, 164.38, 149.72, 176.03, 189.31, 200.16, 0]
HEADxychart-beta
title "HEAD CPU"
x-axis "Elapsed seconds" [1.036, 1.537, 2.538, 4.041, 5.043, 6.545, 7.547, 8.548, 9.049, 10.05, 11.552, 12.553, 14.054, 15.055, 16.557, 17.559, 19.06, 20.062, 21.563, 23.064, 24.065, 25.567, 26.569, 28.071, 29.073, 30.575, 31.575, 33.077, 34.077, 35.579, 36.58, 38.082, 39.083, 39.584, 40.584, 41.586, 43.088, 44.089]
y-axis "CPU percent" 0 --> 200
line [9.99, 129.88, 143.84, 97.89, 179.72, 163.77, 131.62, 189.94, 169.69, 131.78, 63.93, 142.08, 5.98, 4, 111.9, 75.92, 73.96, 57.89, 113.93, 103.79, 131.94, 101.74, 143.57, 139.77, 113.81, 104.01, 93.9, 16, 21.97, 137.84, 91.89, 15.97, 15.98, 0, 130.07, 143.78, 83.78, 103.87]
xychart-beta
title "HEAD memory: RSS then PSS"
x-axis "Elapsed seconds" [0.036, 1.036, 1.537, 2.538, 4.041, 5.043, 6.545, 7.547, 8.548, 9.049, 10.05, 11.552, 12.553, 14.054, 15.055, 16.557, 17.559, 19.06, 20.062, 21.563, 23.064, 24.065, 25.567, 26.569, 28.071, 29.073, 30.575, 31.575, 33.077, 34.077, 35.579, 36.58, 38.082, 39.083, 39.584, 40.584, 41.586, 43.088, 44.089, 45.397]
y-axis "Memory MiB" 0 --> 500
line [12.33, 69.31, 114.01, 125.91, 140.07, 159.93, 165.48, 150.6, 192.39, 176.57, 161.11, 184.12, 194.4, 151.79, 150.59, 162.45, 169.85, 151.52, 173.71, 170.34, 286.42, 204.28, 226.8, 186.43, 175.05, 157.71, 166.84, 159.94, 153.77, 162.43, 247.46, 167.45, 162.94, 161.8, 161.8, 185.13, 177.98, 155.89, 180.29, 0]
line [9.26, 65.95, 110.7, 122.69, 137.07, 156.69, 162.17, 147.2, 190.23, 173.1, 157.72, 180.74, 191.1, 148.4, 147.2, 158.86, 166.28, 148.14, 170.31, 166.98, 284.1, 200.93, 224.1, 184.08, 171.49, 154.32, 163.31, 156.6, 150.33, 159.36, 244.78, 163.44, 159.86, 158.67, 158.23, 181.33, 172.72, 152.4, 176.81, 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. |
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. |
CI Regression ReportSource CI run · source state at render:
Release regression — ✅ HEAD/base failures 0/0; raw binary +0.000098%Package and image size
Startup latency and PSS
Concurrency matrix
Frontend differential — ✅ 1,020/1,020 cases matched; 0 issues; 1 Chromium reference recoveries
Recovered Chromium reference infrastructure failures
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; 616 scenariosWorkers: 4 · cumulative group time: 200.20 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. |
ldm0
force-pushed
the
wpt/performance-generated-receiver-checks
branch
from
October 6, 2026 21:49
e1faad6 to
7158d96
Compare
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
1 participant
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.
Move Performance method/attribute receiver validation into the existing native WebIDL templates. Remove the callback-local private-slot checks and duplicate require_performance_receiver/performance_receiver helpers. Regressions cover forged/inherited objects, author and revoked Proxies, conversion/trap ordering, and genuine cross-realm Performance receivers.
This is one independent commit extracted from the committed wpt-misc-fix snapshot (
7f900e48f8207760967daf2e4cceb0c0bb0f8ee6), adapted to main5fdac079e8912c7e6e79b5f915c99eed57eabf36.Validation of the exact committed tree:
cargo fmt --allcargo clippy --workspace --all-targets --all-features -- -D warningscargo nextest run --no-fail-fast: 19665 passed, 16 existing skips; 32 build jobs and 32 test threads, retries disabled. The local scheduling configuration reserves all test slots for four existing timing-sensitive tests; no new exclusions.Validated and pushed head:
7158d96f35fa41002281258f23ce195b90d47a59.The existing spoofing test now requires TypeError for forged timeOrigin/timing receivers. The first full run exposed its old undefined expectations; those two expectations were strengthened before rerunning all required gates.
The regression module is registered beside browser_api to avoid a registration-only conflict with the independent DOMRect PR. All mandatory gates were rerun after moving that registration.