Skip to content

feat(server-utils): Instrument Vercel AI experimental_evaluate #59029

feat(server-utils): Instrument Vercel AI experimental_evaluate

feat(server-utils): Instrument Vercel AI experimental_evaluate #59029

Re-run triggered September 25, 2026 09:26
Status Failure
Total duration 11m 11s
Artifacts –

build.yml

on: pull_request
Get CI Metadata  /  Get Metadata
7s
Get CI Metadata / Get Metadata
Check lockfile
Check lockfile
Check file formatting
49s
Check file formatting
Check PR branches
5s
Check PR branches
Build Lambda layer
1m 23s
Build Lambda layer
Matrix: job_bundler_plugin_integration_tests
Matrix: job_node_integration_tests
Matrix: job_node_unit_tests
Lint
1m 41s
Lint
Circular Dependency Check
1m 32s
Circular Dependency Check
Browser Unit Tests
2m 27s
Browser Unit Tests
Bun Unit Tests
53s
Bun Unit Tests
Deno Unit Tests
1m 9s
Deno Unit Tests
Cloudflare Integration Tests
6m 43s
Cloudflare Integration Tests
Bun Integration Tests
45s
Bun Integration Tests
Deno Integration Tests
56s
Deno Integration Tests
Check for faulty .d.ts files
38s
Check for faulty .d.ts files
Matrix: job_browser_loader_tests
Matrix: job_browser_playwright_tests
Matrix: job_optional_e2e_tests
Upload Artifacts
Upload Artifacts
Matrix: job_e2e_tests
All required jobs passed or were skipped
6s
All required jobs passed or were skipped
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 notice
[chromium] › tests/errors.server.test.ts:61:3 › server-side errors › captures server route (GET) error: ../../_temp/test-application/tests/errors.server.test.ts#L66
5) [chromium] › tests/errors.server.test.ts:61:3 › server-side errors › captures server route (GET) error Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/server-route-error", waiting until "load" 64 | }); 65 | > 66 | await page.goto('/server-route-error'); | ^ 67 | 68 | const errorEvent = await errorEventPromise; 69 | const errorEventFrames = errorEvent.exception?.values?.[0]?.stacktrace?.frames; at /home/runner/work/_temp/test-application/tests/errors.server.test.ts:66:16
[chromium] › tests/errors.server.test.ts:61:3 › server-side errors › captures server route (GET) error: ../../_temp/test-application/tests/errors.server.test.ts#L0
5) [chromium] › tests/errors.server.test.ts:61:3 › server-side errors › captures server route (GET) error Test timeout of 30000ms exceeded.
[chromium] › tests/errors.server.test.ts:33:3 › server-side errors › captures server load error: ../../_temp/test-application/tests/errors.server.test.ts#L38
4) [chromium] › tests/errors.server.test.ts:33:3 › server-side errors › captures server load error Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/server-load-error", waiting until "load" 36 | }); 37 | > 38 | await page.goto('/server-load-error'); | ^ 39 | 40 | const errorEvent = await errorEventPromise; 41 | const errorEventFrames = errorEvent.exception?.values?.[0]?.stacktrace?.frames; at /home/runner/work/_temp/test-application/tests/errors.server.test.ts:38:16
[chromium] › tests/errors.server.test.ts:33:3 › server-side errors › captures server load error: ../../_temp/test-application/tests/errors.server.test.ts#L0
4) [chromium] › tests/errors.server.test.ts:33:3 › server-side errors › captures server load error Test timeout of 30000ms exceeded.
[chromium] › tests/errors.server.test.ts:5:3 › server-side errors › captures universal load error: ../../_temp/test-application/tests/errors.server.test.ts#L10
3) [chromium] › tests/errors.server.test.ts:5:3 › server-side errors › captures universal load error Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/universal-load-error", waiting until "load" 8 | }); 9 | > 10 | await page.goto('/universal-load-error'); | ^ 11 | 12 | const errorEvent = await errorEventPromise; 13 | const errorEventFrames = errorEvent.exception?.values?.[0]?.stacktrace?.frames; at /home/runner/work/_temp/test-application/tests/errors.server.test.ts:10:16
[chromium] › tests/errors.server.test.ts:5:3 › server-side errors › captures universal load error: ../../_temp/test-application/tests/errors.server.test.ts#L0
3) [chromium] › tests/errors.server.test.ts:5:3 › server-side errors › captures universal load error Test timeout of 30000ms exceeded.
[chromium] › tests/errors.client.test.ts:32:3 › client-side errors › captures universal load error: ../../_temp/test-application/tests/utils.ts#L41
2) [chromium] › tests/errors.client.test.ts:32:3 › client-side errors › captures universal load error Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/", waiting until "load" at utils.ts:41 39 | 40 | await Promise.all([ > 41 | page.goto(route), | ^ 42 | // the test app adds the "hydrated" class to the body when hydrating 43 | page.waitForSelector('body.hydrated'), 44 | // also waiting for the initial pageload span so that later navigations don't interfere at waitForInitialPageload (/home/runner/work/_temp/test-application/tests/utils.ts:41:10) at /home/runner/work/_temp/test-application/tests/errors.client.test.ts:33:11
[chromium] › tests/errors.client.test.ts:32:3 › client-side errors › captures universal load error: ../../_temp/test-application/tests/errors.client.test.ts#L0
2) [chromium] › tests/errors.client.test.ts:32:3 › client-side errors › captures universal load error Test timeout of 30000ms exceeded.
[chromium] › tests/errors.client.test.ts:6:3 › client-side errors › captures error thrown on click: ../../_temp/test-application/tests/utils.ts#L41
1) [chromium] › tests/errors.client.test.ts:6:3 › client-side errors › captures error thrown on click Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/client-error", waiting until "load" at utils.ts:41 39 | 40 | await Promise.all([ > 41 | page.goto(route), | ^ 42 | // the test app adds the "hydrated" class to the body when hydrating 43 | page.waitForSelector('body.hydrated'), 44 | // also waiting for the initial pageload span so that later navigations don't interfere at waitForInitialPageload (/home/runner/work/_temp/test-application/tests/utils.ts:41:10) at /home/runner/work/_temp/test-application/tests/errors.client.test.ts:7:11
[chromium] › tests/errors.client.test.ts:6:3 › client-side errors › captures error thrown on click: ../../_temp/test-application/tests/errors.client.test.ts#L0
1) [chromium] › tests/errors.client.test.ts:6:3 › client-side errors › captures error thrown on click Test timeout of 30000ms exceeded.
🎭 Playwright Run Summary
16 failed [chromium] › tests/errors.client.test.ts:6:3 › client-side errors › captures error thrown on click [chromium] › tests/errors.client.test.ts:32:3 › client-side errors › captures universal load error [chromium] › tests/errors.server.test.ts:5:3 › server-side errors › captures universal load error [chromium] › tests/errors.server.test.ts:33:3 › server-side errors › captures server load error [chromium] › tests/errors.server.test.ts:61:3 › server-side errors › captures server route (GET) error [chromium] › tests/errors.server.test.ts:100:3 › expected errors thrown with `error()` › doesn't capture a 4xx error [chromium] › tests/errors.server.test.ts:122:3 › expected errors thrown with `error()` › captures a 5xx error [chromium] › tests/tracing.client.test.ts:6:3 › client-specific performance events › multiple navigations have distinct traces [chromium] › tests/tracing.client.test.ts:50:3 › client-specific performance events › records manually added component tracking spans [chromium] › tests/tracing.server.test.ts:5:1 › server pageload request span has nested request span for sub request [chromium] › tests/tracing.server.test.ts:167:1 › server trace for a `QUERY` server route includes the wrapped route handler span [chromium] › tests/tracing.test.ts:10:1 › capture a distributed pageload trace ───────────────── [chromium] › tests/tracing.test.ts:54:1 › capture a distributed navigation trace ─────────────── [chromium] › tests/tracing.test.ts:91:1 › record client-side universal load fetch span and trace [chromium] › tests/tracing.test.ts:156:1 › captures a navigation span directly after pageload ── [chromium] › tests/tracing.test.ts:210:1 › captures one navigation span per redirect ─────────── 1 skipped