AppAccessSection › editing flakiness

[nklaassen]

Failure

Link(s) to logs

• https://github.com/gravitational/teleport/actions/runs/13574510727/job/37947342763

Relevant snippet

Summary of all failing tests
FAIL web/packages/teleport/src/Roles/RoleEditor/StandardEditor/Resources.test.tsx (16.119 s)
  ● AppAccessSection › editing

    thrown: "Exceeded timeout of 5000 ms for a test.
    Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

      311 |     within(gcpServiceAccounts()).getAllByRole('textbox');
      312 |
    > 313 |   test('editing', async () => {
          |   ^
      314 |     const { user, onChange } = setup();
      315 |     await user.click(screen.getByRole('button', { name: 'Add a Label' }));
      316 |     await user.type(screen.getByPlaceholderText('label key'), 'env');

      at test (web/packages/teleport/src/Roles/RoleEditor/StandardEditor/Resources.test.tsx:313:3)
      at Object.describe (web/packages/teleport/src/Roles/RoleEditor/StandardEditor/Resources.test.tsx:282:1)


Seed:        -1503809771
Test Suites: 1 failed, 288 passed, 289 total
Tests:       1 failed, 1667 passed, 1668 total
Snapshots:   1 passed, 1 total
Time:        103.159 s
Ran all test suites.
 ELIFECYCLE  Test failed. See above for more details.
Error: Process completed with exit code 1.

[hugoShaka]

Hit this one as well, in the Actions page we see the flakiness started an hour ago: https://github.com/gravitational/teleport/actions/workflows/unit-tests-ui.yaml

The timeout might be reached because we are all rushing to get our PRs in 17.3 and this causes substantial server load.