Confirm e2e failures from backend source-formatting deploy - #10657
Conversation
Confirming that the two deterministic e2e failures (sourcemap_stacktrace, jump-to-code-01_basic) reproduce on any new PR after the Aug 20 backend controllers deploy, independent of devtools changes.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Confirmed. This PR is an empty commit on top of main (2c49b9a), and e2e fails, while the Nightly runs on that same SHA were green on Aug 19 and Aug 20 08:12 UTC — before the backend controllers deploy at 09:42 UTC. Failed (all retries):
Note Next step: update the affected test expectations (or revisit the threshold) — follow-ups on this branch. |
E2E Tests
|
Draft PR with an empty commit, purely to run e2e CI.
isMinifiedlong-line threshold went 500 → 200 chars, soregeneratorRuntime.js(and a few other CRA sources) are now classified minified and get pretty-printed.sourcemap_stacktracefails: frames report pretty-printed linesregeneratorRuntime.js:136/:72instead of the raw:125/:69the test expects.jump-to-code-01_basicfails at the first check: "Jump to code" where the test expects "No results".If CI here shows the same two failures, the fix is updating these test expectations (follow-up commits on this branch).