Process completed with exit code 1.

Process completed with exit code 1.

One or more integration shards failed

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-1790080858128-l3ph76x@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-1790080858128-l3ph76x@hyperdx.io's Team</span> - unexpected value "e2e-test-1790080858128-l3ph76x@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

1) [chromium] › tests/e2e/features/search/relative-time.spec.ts:53:9 › Relative Time Picker › Relative Time Options › should select different relative time intervals @relative-time › Select Last 15 minutes TimeoutError: locator.waitFor: Timeout 5000ms exceeded. Call log: - waiting for getByTestId('time-picker-relative-switch') at components/TimePickerComponent.ts:175 173 | */ 174 | async isRelativeTimeEnabled(): Promise<boolean> { > 175 | await this.relativeTimeSwitch.waitFor({ state: 'attached', timeout: 5000 }); | ^ 176 | return await this.relativeTimeSwitch.isChecked(); 177 | } 178 | at TimePickerComponent.isRelativeTimeEnabled (/home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/components/TimePickerComponent.ts:175:35) at TimePickerComponent.enableRelativeTime (/home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/components/TimePickerComponent.ts:183:34) at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/relative-time.spec.ts:72:39 at /home/runner/work/hyperdx/hyperdx/packages/app/tests/e2e/features/search/relative-time.spec.ts:64:9

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. 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/team.spec.ts:132:7 › Team Settings Page › should cancel team name editing @team @full-stack 1 skipped 93 passed (3.8m)

96 passed (4.0m)

95 passed (5.5m)