Fix fetch stack test on deploy

vercel · Jan 28, 2023 · bcd63af · bcd63af
1 parent 6e73650
commit bcd63af
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/...tack-traces-in-edge-runtime/fetch-failures-have-good-stack-traces-in-edge-runtime.test.ts b/...tack-traces-in-edge-runtime/fetch-failures-have-good-stack-traces-in-edge-runtime.test.ts
@@ -12,10 +12,12 @@ createNextDescribe(
   'fetch failures have good stack traces in edge runtime',
   {
     files: __dirname,
+    // don't have access to runtime logs on deploy
+    skipDeployment: true,
   },
   ({ next, isNextStart, isNextDev }) => {
     it('when awaiting `fetch` using an unknown domain, stack traces are preserved', async () => {
-      const browser = await webdriver(next.appPort, '/api/unknown-domain')
+      const browser = await webdriver(next.url, '/api/unknown-domain')
 
       if (isNextStart) {
         expect(next.cliOutput).toMatch(/at.+\/pages\/api\/unknown-domain.js/)
@@ -34,7 +36,7 @@ createNextDescribe(
     })
 
     it('when returning `fetch` using an unknown domain, stack traces are preserved', async () => {
-      await webdriver(next.appPort, '/api/unknown-domain-no-await')
+      await webdriver(next.url, '/api/unknown-domain-no-await')
       await check(
         () => stripAnsi(next.cliOutput),
         /at.+\/pages\/api\/unknown-domain-no-await.js/