Process completed with exit code 1.

2) [chromium] › amplitron.spec.ts:318:7 › No Runtime Errors › no uncaught exceptions during the full load cycle Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toHaveLength(expected) Expected length: 0 Received length: 1 Received array: [[SyntaxError: await is only valid in async functions and the top level bodies of modules]] 322 | await page.waitForSelector('#loading.hidden', { timeout: 60_000 }); 323 | > 324 | expect(log.errors).toHaveLength(0); | ^ 325 | }); 326 | 327 | test('no WASM abort() or RuntimeError: unreachable panics', async ({ page }) => { at /home/runner/work/Amplitron/Amplitron/tests/web/amplitron.spec.ts:324:24

2) [chromium] › amplitron.spec.ts:318:7 › No Runtime Errors › no uncaught exceptions during the full load cycle Error: expect(received).toHaveLength(expected) Expected length: 0 Received length: 1 Received array: [[SyntaxError: await is only valid in async functions and the top level bodies of modules]] 322 | await page.waitForSelector('#loading.hidden', { timeout: 60_000 }); 323 | > 324 | expect(log.errors).toHaveLength(0); | ^ 325 | }); 326 | 327 | test('no WASM abort() or RuntimeError: unreachable panics', async ({ page }) => { at /home/runner/work/Amplitron/Amplitron/tests/web/amplitron.spec.ts:324:24

1) [chromium] › amplitron.spec.ts:51:7 › Page Load & WASM Initialisation › page loads without JavaScript errors Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toHaveLength(expected) Expected length: 0 Received length: 1 Received array: [[SyntaxError: await is only valid in async functions and the top level bodies of modules]] 58 | 59 | // No uncaught JS exceptions on the initial page load > 60 | expect(log.errors).toHaveLength(0); | ^ 61 | }); 62 | 63 | test('loading overlay is visible on initial page load', async ({ page }) => { at /home/runner/work/Amplitron/Amplitron/tests/web/amplitron.spec.ts:60:24

1) [chromium] › amplitron.spec.ts:51:7 › Page Load & WASM Initialisation › page loads without JavaScript errors Error: expect(received).toHaveLength(expected) Expected length: 0 Received length: 1 Received array: [[SyntaxError: await is only valid in async functions and the top level bodies of modules]] 58 | 59 | // No uncaught JS exceptions on the initial page load > 60 | expect(log.errors).toHaveLength(0); | ^ 61 | }); 62 | 63 | test('loading overlay is visible on initial page load', async ({ page }) => { at /home/runner/work/Amplitron/Amplitron/tests/web/amplitron.spec.ts:60:24

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026