Conversation
The http2 rewrite (6ef5977) quarantined its own regression suites while the engine was still being reconciled. All three now pass 3/3 on darwin-arm64, linux-x64, and windows-x64 against 1.4.0-canary.1+c4fad462e: node-http2.test.js 294 pass / 6 skip / 0 fail / 12217 expect() h2-conformance.test.ts 37 pass / 0 fail / 66 expect() / 2 snapshots node-http2-invalid-padding.test.ts 7 pass / 0 fail / 22 expect() These entries carried no platform modifier, so getRelevantTests in scripts/runner.node.mjs removed the files from every lane, leaving the rewritten engine with its own regression suite switched off. The [ ASAN ] prefix skip for test/js/node/http2/ and the platform-scoped [ LINUX ]/[ WINDOWS ] parallel-suite entries remain; they cover separate socket-layer issues and are out of scope here.
|
Verified 3/3 on darwin-arm64 (reported), linux-x64, and windows-x64 against canary c4fad46. The ASAN lane still skips this directory via the existing CI (build #73699, final): the three unquarantined http2 suites passed on every lane. No http2-related failures anywhere in the build. Remaining red, all unrelated to this diff:
This diff only deletes lines from |
|
Updated 1:33 AM PT - Jul 16th, 2026
❌ @robobun, your commit b618f43 has 3 failures in
🧪 To try this PR locally: bunx bun-pr 34307That installs a local version of the PR into your bun-34307 --bun |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
WalkthroughChangesHTTP/2 test expectations
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Comment |
There was a problem hiding this comment.
This is a clean, self-correcting change (removing three stale quarantine entries so the http2 suites run again), but test/expectations.txt is CODEOWNER-protected, so leaving it for a human sign-off.
What was reviewed:
- Confirmed the three removed entries are unmodified (no platform prefix) and the referenced test files exist.
- Verified the
[ ASAN ] test/js/node/http2/prefix skip and the platform-scopedtest-http2-*entries are untouched, matching the PR's stated scope. - Checked that no other lines were touched — pure deletion of the reconciliation block and its comment.
Extended reasoning...
Overview
The PR deletes 8 lines from test/expectations.txt: a 5-line explanatory comment block plus three unmodified [ FAIL ] quarantine entries for test/js/node/http2/node-http2.test.js, h2-conformance.test.ts, and node-http2-invalid-padding.test.ts. These were added during the http2 rewrite (#31584) while the Bun-owned suites were being reconciled with the new engine. The PR description reports 3/3 clean runs on darwin-arm64, linux-x64, and windows-x64 against canary c4fad46.
Security risks
None. No source code is touched; this only re-enables existing test files in the CI runner. The change is additive to coverage, not subtractive.
Level of scrutiny
Low on the mechanics — the diff is a pure deletion from a plain-text expectations list, and the failure mode (tests turn out to still fail on some lane) is self-correcting via CI. However, .github/CODEOWNERS explicitly assigns /test/expectations.txt to Jarred-Sumner, which per my guidelines means a human owner should sign off regardless of change simplicity.
Other factors
- The three test files exist on disk and are substantial (338 tests / ~12k assertions per the PR).
- The retained
[ ASAN ] test/js/node/http2/ [ SKIP ]prefix entry means the ASAN lane is unaffected, consistent with the PR's out-of-scope note. - No prior reviews or outstanding comments on the timeline; robobun confirmed the 3/3 verification independently.
- Worst-case downside is a red CI lane, which would surface immediately on build #73699.
|
Closing as part of a cleanup of stale pull requests. This PR has had no new commits since 2026-07-16, it conflicts with main, and its last CI run failed. This is not a judgment on the fix itself. If the problem still reproduces on a current build, reopen this PR after a rebase or open a new one against main. |
The http2 rewrite (6ef5977, #31584) quarantined its own regression suites at
test/expectations.txt:243-245while the engine was still being reconciled with the legacy parser's expectations. The reconciliation is done: all three files now pass cleanly, but the entries were never removed, so the rewritten engine has been shipping with its own regression suite switched off on every lane.What was quarantined
No platform modifier, so
getRelevantTestsinscripts/runner.node.mjsspliced these out ofavailableTestson every platform.Verification
3/3 consecutive runs, exit 0, on
1.4.0-canary.1+c4fad462e:338 tests / 12,305 expect() calls back in the run.
Out of scope
[ ASAN ] test/js/node/http2/ [ SKIP ]stays: it covers a separate socket-layer connect-race lifetime report and is ASAN-only.[ LINUX ]/[ WINDOWS ]entries fortest/js/node/test/parallel/test-http2-*stay: platform-scoped, separate socket-layer issue, need per-platform re-triage before touching.no test proof · iteration 0 · docs-only change; test-proof not applicable