Process completed with exit code 1.

1) [chromium] › tests/e2e/features/search/custom-time-range.spec.ts:66:7 › Custom Time Range › should preserve typed times after closing and reopening the picker @custom-time-range › Reopen picker and verify inputs still show typed times Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveValue(expected) failed Locator: getByTestId('time-picker-popover').getByPlaceholder('YYYY-MM-DD HH:mm:ss').nth(1) Expected: "2026-04-10 11:45:20" Timeout: 5000ms Error: element(s) not found Call log: - Expect "toHaveValue" with timeout 5000ms - waiting for getByTestId('time-picker-popover').getByPlaceholder('YYYY-MM-DD HH:mm:ss').nth(1) 75 | await searchPage.timePicker.open(); 76 | await expect(searchPage.timePicker.startDateInput).toHaveValue(start); > 77 | await expect(searchPage.timePicker.endDateInput).toHaveValue(end); | ^ 78 | }); 79 | }); 80 | at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/custom-time-range.spec.ts:77:56 at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/custom-time-range.spec.ts:74:5

1) [chromium] › tests/e2e/features/search/custom-time-range.spec.ts:66:7 › Custom Time Range › should preserve typed times after closing and reopening the picker @custom-time-range › Reopen picker and verify inputs still show typed times Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveValue(expected) failed Locator: getByTestId('time-picker-popover').getByPlaceholder('YYYY-MM-DD HH:mm:ss').first() Expected: "2026-04-10 09:15:30" Timeout: 5000ms Error: element(s) not found Call log: - Expect "toHaveValue" with timeout 5000ms - waiting for getByTestId('time-picker-popover').getByPlaceholder('YYYY-MM-DD HH:mm:ss').first() 74 | await test.step('Reopen picker and verify inputs still show typed times', async () => { 75 | await searchPage.timePicker.open(); > 76 | await expect(searchPage.timePicker.startDateInput).toHaveValue(start); | ^ 77 | await expect(searchPage.timePicker.endDateInput).toHaveValue(end); 78 | }); 79 | }); at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/custom-time-range.spec.ts:76:58 at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/custom-time-range.spec.ts:74:5

1) [chromium] › tests/e2e/features/search/custom-time-range.spec.ts:66:7 › Custom Time Range › should preserve typed times after closing and reopening the picker @custom-time-range › Reopen picker and verify inputs still show typed times Error: expect(locator).toHaveValue(expected) failed Locator: getByTestId('time-picker-popover').getByPlaceholder('YYYY-MM-DD HH:mm:ss').nth(1) Expected: "2026-04-10 11:45:20" Timeout: 5000ms Error: element(s) not found Call log: - Expect "toHaveValue" with timeout 5000ms - waiting for getByTestId('time-picker-popover').getByPlaceholder('YYYY-MM-DD HH:mm:ss').nth(1) 75 | await searchPage.timePicker.open(); 76 | await expect(searchPage.timePicker.startDateInput).toHaveValue(start); > 77 | await expect(searchPage.timePicker.endDateInput).toHaveValue(end); | ^ 78 | }); 79 | }); 80 | at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/custom-time-range.spec.ts:77:56 at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/custom-time-range.spec.ts:74:5

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/