{{ message }}
Repository navigation
Conversation
CI Regression ReportSource CI run · source state at render:
Release regression — ✅ HEAD/base failures 0/0; raw binary +0.081009%Package and image size
Startup latency and PSS
Concurrency matrix
Frontend differential — ❌ 1,019/1,020 cases matched; 1 issues
First failing cases
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: 197.14 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 quarterRaw 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. |
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.
Concurrent compatible image consumers in one Document currently start duplicate HTTP transfers. Share pending transfers while preserving exact response bytes and network observations. Each consumer keeps independent cancellation; dropping the last consumer cancels the transport. Failed loads are not retained, and no-store/private response headers prevent later consumers from joining.
Keep request credentials, policy revisions, mode, referrer policy, integrity and cache bypasses separate. The registry holds bounded weak entries rather than owning completed responses. Gated HTTP regressions cover sharing, streaming, independent cancellation, last-consumer teardown, failures and policy boundaries.
The long Service Worker navigation test keeps each awaited navigation future on the heap to bound debug-build stack use. All navigation scenarios and assertions remain covered. Before this test-harness adaptation, the extracted change reproduced stack overflow in 3/3 isolated runs; the original integrated branch already contained the adaptation.
Extracted independently from
window.chromeonto main87527dec85.Validation on this exact source tree:
cargo fmt --allcargo clippy --workspace --all-targets --all-features -- -D warningscargo nextest run --no-fail-fast --flaky-result fail --status-level fail: Summary [ 127.643s] 20522 tests run: 20522 passed (9 slow), 18 skipped. Automatic retries are disabled.