1) [chromium] › tests/e2e/features/search/search-filters.spec.ts:74:7 › Search Filters › Should pin filter and verify it persists after reload @search TimeoutError: locator.click: Timeout 10000ms exceeded. Call log: - waiting for getByRole('menuitem', { name: 'Pin for me' }) - locator resolved to <button type="button" tabindex="-1" role="menuitem" data-menu-item="true" data-mantine-stop-propagation="true" class="focus_focusRing__UFS1R m_99ac2aa1 mantine-Menu-item m_87cf2631 mantine-UnstyledButton-root">…</button> - attempting click action 2 × waiting for element to be visible, enabled and stable - element is not visible - retrying click action - waiting 20ms 2 × waiting for element to be visible, enabled and stable - element is not visible - retrying click action - waiting 100ms 18 × waiting for element to be visible, enabled and stable - element is not visible - retrying click action - waiting 500ms at components/FilterComponent.ts:127 125 | await this.page 126 | .getByRole('menuitem', { name: 'Pin for me' }) > 127 | .click({ timeout: 10000 }); | ^ 128 | } 129 | 130 | /** at FilterComponent.pinFilter (/home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/components/FilterComponent.ts:127:8) at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/search-filters.spec.ts:75:5

1) [chromium] › tests/e2e/features/team.spec.ts:132:7 › Team Settings Page › should cancel team name editing @team @full-stack › Verify original name is still displayed Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('team-name-display') Expected: "My team" Received: "e2e-test-1787276876133-3avt6ow@hyperdx.io's Team" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('team-name-display') 9 × locator resolved to <span data-testid="team-name-display">e2e-test-1787276876133-3avt6ow@hyperdx.io's Team</span> - unexpected value "e2e-test-1787276876133-3avt6ow@hyperdx.io's Team" 148 | 149 | await test.step('Verify original name is still displayed', async () => { > 150 | await expect(teamPage.teamNameValue).toHaveText(originalName!); | ^ 151 | await expect(teamPage.teamNameSave).toBeHidden(); 152 | }); 153 | }); at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/team.spec.ts:150:44 at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/team.spec.ts:149:16

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4, actions/cache/save@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

1 flaky [chromium] › tests/e2e/features/search/search-filters.spec.ts:74:7 › Search Filters › Should pin filter and verify it persists after reload @search 76 passed (4.2m)

1 flaky [chromium] › tests/e2e/features/team.spec.ts:132:7 › Team Settings Page › should cancel team name editing @team @full-stack 1 skipped 75 passed (4.4m)

78 passed (4.6m)