Skip to content

Commit c3559c9

Browse files
authored
test: use a unique deploy alias per test group to avoid deploy concurrency issues (#2964)
* test: use a unique deploy alias per test group See inline comment. * test(deps): pin netlify-cli for now There was a regression introduced in 21.3.0 and fixed in 22.0.0 But we cannot bump to 22.0.0 at the moment. The regression causes builds to auto-install the Neon extension unconditionally.
1 parent 32c4acc commit c3559c9

File tree

4 files changed

+99
-94
lines changed

4 files changed

+99
-94
lines changed

.github/workflows/test-e2e.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -198,6 +198,10 @@ jobs:
198198
NODE_ENV: production
199199
NEXT_EXTERNAL_TESTS_FILTERS: ${{ steps.test-filters.outputs.filters }}
200200
NEXT_TEST_SKIP_RETRY_MANIFEST: ${{ steps.test-filters.outputs.skip-retry }}
201+
# Use a unique alias per test matrix group and shard. Otherwise, a deploy within
202+
# one job may wait for deploys in other jobs (only one deploy may be in progress for
203+
# a given alias at a time), resulting in cascading timeouts.
204+
DEPLOY_ALIAS: vercel-next-e2e-${{ matrix.version_spec.selector }}-${{ matrix.group }}
201205
run: node run-tests.js -g ${{ matrix.group }}/${{ needs.setup.outputs.total }} -c ${TEST_CONCURRENCY} --type e2e
202206
working-directory: ${{ env.next-path }}
203207

0 commit comments

Comments
 (0)