4) [chromium] › tests/e2e/dashboard/error-handling.spec.ts:111:3 › Error Handling and Network Failures › Application handles malformed API responses Error: expect(locator).toBeVisible() failed Locator: locator('[data-testid="main-content"], main, [role="main"]') Expected: visible Timeout: 15000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 15000ms - waiting for locator('[data-testid="main-content"], main, [role="main"]') 122 | 123 | // App should handle JSON parse errors gracefully > 124 | await expect(page.locator('[data-testid="main-content"], main, [role="main"]')).toBeVisible(); | ^ 125 | 126 | // Check that navigation still works 127 | const navigation = page.locator('nav, [data-testid="navigation"], [data-testid="sidebar"]'); at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/dashboard/error-handling.spec.ts:124:85

3) [chromium] › tests/e2e/dashboard/error-handling.spec.ts:86:3 › Error Handling and Network Failures › Application handles slow network conditions Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: locator('[data-testid="main-content"], main, [role="main"]') Expected: visible Timeout: 15000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 15000ms - waiting for locator('[data-testid="main-content"], main, [role="main"]') 102 | 103 | // Should show main content even while API calls are slow > 104 | await expect(page.locator('[data-testid="main-content"], main, [role="main"]')).toBeVisible(); | ^ 105 | 106 | // Navigation should work despite slow API 107 | const navigation = page.locator('nav, [data-testid="navigation"], [data-testid="sidebar"]'); at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/dashboard/error-handling.spec.ts:104:85

3) [chromium] › tests/e2e/dashboard/error-handling.spec.ts:86:3 › Error Handling and Network Failures › Application handles slow network conditions Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: locator('[data-testid="main-content"], main, [role="main"]') Expected: visible Timeout: 15000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 15000ms - waiting for locator('[data-testid="main-content"], main, [role="main"]') 102 | 103 | // Should show main content even while API calls are slow > 104 | await expect(page.locator('[data-testid="main-content"], main, [role="main"]')).toBeVisible(); | ^ 105 | 106 | // Navigation should work despite slow API 107 | const navigation = page.locator('nav, [data-testid="navigation"], [data-testid="sidebar"]'); at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/dashboard/error-handling.spec.ts:104:85

3) [chromium] › tests/e2e/dashboard/error-handling.spec.ts:86:3 › Error Handling and Network Failures › Application handles slow network conditions Error: expect(locator).toBeVisible() failed Locator: locator('[data-testid="main-content"], main, [role="main"]') Expected: visible Timeout: 15000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 15000ms - waiting for locator('[data-testid="main-content"], main, [role="main"]') 102 | 103 | // Should show main content even while API calls are slow > 104 | await expect(page.locator('[data-testid="main-content"], main, [role="main"]')).toBeVisible(); | ^ 105 | 106 | // Navigation should work despite slow API 107 | const navigation = page.locator('nav, [data-testid="navigation"], [data-testid="sidebar"]'); at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/dashboard/error-handling.spec.ts:104:85

2) [chromium] › tests/e2e/dashboard/error-handling.spec.ts:59:3 › Error Handling and Network Failures › Application handles API network failures Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: locator('[data-testid="main-content"], main, [role="main"]') Expected: visible Timeout: 15000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 15000ms - waiting for locator('[data-testid="main-content"], main, [role="main"]') 67 | 68 | // Wait for initial load > 69 | await expect(page.locator('[data-testid="main-content"], main, [role="main"]')).toBeVisible(); | ^ 70 | 71 | // Check that the app shows appropriate error states for failed requests 72 | // (App should handle failures gracefully without crashing) at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/dashboard/error-handling.spec.ts:69:85

2) [chromium] › tests/e2e/dashboard/error-handling.spec.ts:59:3 › Error Handling and Network Failures › Application handles API network failures Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: locator('[data-testid="main-content"], main, [role="main"]') Expected: visible Timeout: 15000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 15000ms - waiting for locator('[data-testid="main-content"], main, [role="main"]') 67 | 68 | // Wait for initial load > 69 | await expect(page.locator('[data-testid="main-content"], main, [role="main"]')).toBeVisible(); | ^ 70 | 71 | // Check that the app shows appropriate error states for failed requests 72 | // (App should handle failures gracefully without crashing) at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/dashboard/error-handling.spec.ts:69:85

2) [chromium] › tests/e2e/dashboard/error-handling.spec.ts:59:3 › Error Handling and Network Failures › Application handles API network failures Error: expect(locator).toBeVisible() failed Locator: locator('[data-testid="main-content"], main, [role="main"]') Expected: visible Timeout: 15000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 15000ms - waiting for locator('[data-testid="main-content"], main, [role="main"]') 67 | 68 | // Wait for initial load > 69 | await expect(page.locator('[data-testid="main-content"], main, [role="main"]')).toBeVisible(); | ^ 70 | 71 | // Check that the app shows appropriate error states for failed requests 72 | // (App should handle failures gracefully without crashing) at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/dashboard/error-handling.spec.ts:69:85

1) [chromium] › tests/e2e/auth/basic.spec.ts:4:3 › Authentication - New UI Only › Protected routes in new UI handle authentication correctly Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.isVisible: Error: strict mode violation: locator('[data-testid="main-content"], main, [role="main"]') resolved to 3 elements: 1) <main class="min-h-screen">…</main> aka getByRole('main').first() 2) <main class="col-span-12 w-full">…</main> aka getByRole('main').nth(1) 3) <main class="settings-page-content" aria-label="Main settings configuration">…</main> aka getByRole('main', { name: 'Main settings configuration' }) Call log: - checking visibility of locator('[data-testid="main-content"], main, [role="main"]') 28 | const hasSettingsContent = await page 29 | .locator('[data-testid="main-content"], main, [role="main"]') > 30 | .isVisible(); | ^ 31 | 32 | if (isRedirectedToLogin || hasLoginForm) { 33 | // Assert we were redirected or show login form at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/auth/basic.spec.ts:30:8

1) [chromium] › tests/e2e/auth/basic.spec.ts:4:3 › Authentication - New UI Only › Protected routes in new UI handle authentication correctly Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.isVisible: Error: strict mode violation: locator('[data-testid="main-content"], main, [role="main"]') resolved to 3 elements: 1) <main class="min-h-screen">…</main> aka getByRole('main').first() 2) <main class="col-span-12 w-full">…</main> aka getByRole('main').nth(1) 3) <main class="settings-page-content" aria-label="Main settings configuration">…</main> aka getByRole('main', { name: 'Main settings configuration' }) Call log: - checking visibility of locator('[data-testid="main-content"], main, [role="main"]') 28 | const hasSettingsContent = await page 29 | .locator('[data-testid="main-content"], main, [role="main"]') > 30 | .isVisible(); | ^ 31 | 32 | if (isRedirectedToLogin || hasLoginForm) { 33 | // Assert we were redirected or show login form at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/auth/basic.spec.ts:30:8

1) [chromium] › tests/e2e/auth/basic.spec.ts:4:3 › Authentication - New UI Only › Protected routes in new UI handle authentication correctly Error: locator.isVisible: Error: strict mode violation: locator('[data-testid="main-content"], main, [role="main"]') resolved to 3 elements: 1) <main class="min-h-screen">…</main> aka getByRole('main').first() 2) <main class="col-span-12 w-full">…</main> aka getByRole('main').nth(1) 3) <main class="settings-page-content" aria-label="Main settings configuration">…</main> aka getByRole('main', { name: 'Main settings configuration' }) Call log: - checking visibility of locator('[data-testid="main-content"], main, [role="main"]') 28 | const hasSettingsContent = await page 29 | .locator('[data-testid="main-content"], main, [role="main"]') > 30 | .isVisible(); | ^ 31 | 32 | if (isRedirectedToLogin || hasLoginForm) { 33 | // Assert we were redirected or show login form at /home/runner/work/birdnet-go/birdnet-go/frontend/tests/e2e/auth/basic.spec.ts:30:8

Canceling since a higher priority waiting request for e2e-Frontend E2E Tests-refs/pull/2433/merge exists

The operation was canceled.

Canceling since a higher priority waiting request for e2e-Frontend E2E Tests-refs/pull/2433/merge exists

The operation was canceled.

Canceling since a higher priority waiting request for e2e-Frontend E2E Tests-refs/pull/2433/merge exists

The operation was canceled.

Canceling since a higher priority waiting request for e2e-Frontend E2E Tests-refs/pull/2433/merge exists

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-task@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-task@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No files were found with the provided path: frontend/blob-report/. No artifacts will be uploaded.

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-task@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No files were found with the provided path: frontend/blob-report/. No artifacts will be uploaded.

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: arduino/setup-task@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No files were found with the provided path: frontend/blob-report/. No artifacts will be uploaded.

Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2