1) [firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result Test timeout of 270000ms exceeded.

1) [firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result Error: locator.click: Test timeout of 270000ms exceeded. Call log: - waiting for getByTestId('scenario-timetable-train').nth(9).getByTestId('scenario-timetable-train-button') - locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div> - attempting click action - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - performing click action - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #2 - waiting 20ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #3 - waiting 100ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-toolbar">…</div> intercepts pointer events - retrying click action, attempt #4 - waiting 100ms - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying - locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div> - attempting click action - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-toolbar">…</div> intercepts pointer events - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - performing click action - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #2 - waiting 20ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #3 - waiting 100ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-toolbar">…</div> intercepts pointer events - retrying click action, attempt #4 - waiting 100ms - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying - locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div> - attempting click action - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-toolbar">…</div> intercepts pointer events - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - performing click action

1) [firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 270000ms exceeded.

1) [firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.click: Test timeout of 270000ms exceeded. Call log: - waiting for getByTestId('scenario-timetable-train').nth(11).getByTestId('scenario-timetable-train-button') - locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div> - attempting click action - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - performing click action - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #2 - waiting 20ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #3 - waiting 100ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <button type="button" class="filter-button" data-testid=…>…</button> from <div class="sticky-filter">…</div> subtree intercepts pointer events - retrying click action, attempt #4 - waiting 100ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <button type="button" class="filter-button" data-testid=…>…</button> from <div class="sticky-filter">…</div> subtree intercepts pointer events - retrying click action, attempt #5 - waiting 500ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #6 - waiting 500ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="scenario-timetable-trains">…</div> intercepts pointer events - retrying click action, attempt #7 - waiting 500ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <button type="button" class="filter-button" data-testid=…>…</button> from <div class="sticky-filter">…</div> subtree intercepts pointer events - retrying click action, attempt #8 - waiting 500ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <button type="button" class="filter-button" data-testid=…>…</button> from <div class="sticky-filter">…</div> subtree intercepts pointer events - retrying click action, attempt #9 - waiting 500ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - performing click action - <div class="scenario-timetable-trains">…</div> intercepts pointer events -

2) [webkit] › 013-stdcm-simulation-sheet.spec.ts:60:7 › Verify stdcm simulation page › Verify STDCM stops and simulation sheet TimeoutError: locator.waitFor: Timeout 60000ms exceeded. Call log: - waiting for locator('.stdcm-results .simulation-list') to be visible at pages/stdcm-page-model.ts:617 615 | await this.launchSimulationButton.click({ force: true }); 616 | // Wait for simulation elements to load and validate their presence > 617 | await this.simulationList.waitFor({ timeout: 60_000 }); | ^ 618 | const simulationElements = await this.simulationList.all(); 619 | 620 | if (simulationElements.length < MINIMUM_SIMULATION_NUMBER) { at STDCMPage.launchSimulation (/app/front/tests/pages/stdcm-page-model.ts:617:31) at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:80:5

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636

[webkit] › 012-op-simulation-settings-tab.spec.ts took 2.0m

[webkit] › 008-train-schedule.spec.ts took 1.5m

[webkit] › 009-rollingstock-editor.spec.ts took 59.0s

[firefox] › 012-op-simulation-settings-tab.spec.ts took 55.3s

[firefox] › 006-stdcm.spec.ts took 52.7s