[test] Fix new deploy suites (#99162)
The `test-e2e-deploy-release` run for `v16.4.0-canary.43` failed three
webpack shards deterministically
([run](https://github.com/vercel/next.js/actions/runs/35989345663))
after #98847 and #98848 removed the deploy-mode exclusions.
On PRs we only run deploy tests for Turbopack so these failures were
missed.
- `use-cache-segment-configs`: #98847 added a deploy-specific snapshot
for Turbopack, but the webpack path still used the local snapshot.
Vercel's fetched build logs strip code-frame indentation and trailing
whitespace, so the deployed output can never match it. The webpack
assertion now has its own deploy branch with the exact formatting Vercel
produces.
- `app-edge-invalid-reexport`: #98848 removed `skipDeployment`, but the
fixture exports `preferredRegion = 'test-region'`, which the Vercel
platform rejects during deployment (`Invalid region: test-region`). The
test now overrides the basic page with a valid region (`iad1`) in deploy
mode. The asserted re-export warnings are build-time diagnostics, so the
region value does not affect them.
- `deprecation-warnings`: both tests call `next.start()` inside the test
body, which `e2e-utils` caps at 60 seconds when no explicit timeout is
given. Deployments now take about two minutes (`Ready in 2m`, up from
`Ready in 1m` in the passing canary.42 run with the same Vercel CLI
59.26.0), so both tests time out on every run. They now pass an explicit
240-second timeout, matching the other deploy tests.
---------
Co-authored-by: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
