Unverified Commit 8ac283a2 authored by Marcos Hernanz's avatar Marcos Hernanz Committed by GitHub

Regenerate Rspack test manifests from the latest canary run

The `test rspack dev` / `test rspack production` jobs filter suites
through `test/rspack-{dev,build}-tests-manifest.json`. These legacy
(unversioned) manifests auto-include any suite they do not list, so
they only work while they track the tree.

They have not been regenerated since 2026-04-18. The daily "Update
Rspack test manifest" workflow runs `gh api` without `GH_TOKEN`,
`test/update-bundler-manifest.js` expects the self-hosted runner path
(`/root/actions-runner/...`) while the Rspack artifacts come from
GitHub-hosted runners (`/home/runner/work/...`), and the
`rspack-nextjs-{dev,build}-integration-tests` workflows that produce the
`test-results-rspack-*` artifacts have failed at startup since
2026-08-21. Meanwhile #93247 moved many suites from `test/integration`
to `test/e2e` and `test/development`; the manifests still list the old
paths, so the moved suites run with every case enabled and all known
Rspack parity gaps fail the jobs.

Regenerated both manifests from the last available
`test-results-rspack-{development,production}` artifacts (2026-08-20,
canary e2fb664c) with the same `--override` semantics the workflow
uses for Rspack. Every case that failed in this PR's Rspack jobs is
recorded as failing in that run and is now excluded; the suites this
PR relies on for verification (`error-ignored-frames`, `browser-logs`,
`owner-stack-react-missing-key-prop`) stay enabled.
parent c9b536e4
This diff is collapsed.
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment