[test] Expose first-run e2e test failures in CI (#99528)
PR #89929 added automatic retries of individual e2e tests to reduce CI time. These retries reuse the fixture without rerunning `beforeAll`. A failed attempt can write an ISR cache or change other state. The retry can then pass against a different starting state, potentially hiding a real issue. Each CI test job runs a shard containing multiple test files. Previously, rerunning a failed job also reran the files that had already passed. PR #92832 caches passing results so a job rerun can skip those files and rerun only the failed files. This reduces both retry cost and time, allowing us to remove the individual-test retries. This change preserves the timeout improvements from #89929. It also removes the redundant retry opt-out and updates stale comments and test-gate documentation. The retry removal also exposed test assumptions that required these changes: - Both concurrent root-param cache tests now exclude deploy mode. Cross-request deduplication requires requests to share a server process, but deployed requests can reach different function instances. The tests remain enabled in dev and `next start`. - Both affected App Shell tests now refresh and repeat only the preparatory prefetch until root-specific shell segments arrive. Deploy can initially serve generic fallback segments while ISR generates a shell for unprerendered root params; `next start` generates that shell blockingly. The cache-reuse and navigation assertions remain outside the retry. The static-shell test also loads a fresh home page to prevent BFCache from restoring visible accordions, then primes both language variants. The TODOs leave the direction for consolidating the serving behavior open. The [deploy run and rerun](https://github.com/vercel/next.js/actions/runs/36878368304/attempts/2) exposed the failures addressed by these test corrections.
Showing
Please
register
or
sign in
to comment