1) [webkit] › 006-stdcm.spec.ts:102:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet Error: Timeout 90000ms exceeded while waiting on the predicate at pages/stdcm-page-model.ts:696 694 | await download.saveAs(downloadPath); 695 | logger.info(`The PDF was successfully downloaded to: ${downloadPath}`); > 696 | }).toPass({ | ^ 697 | timeout: EXPECT_TO_PASS_TIMEOUT, 698 | }); 699 | } at STDCMPage.downloadSimulation (/app/front/tests/pages/stdcm-page-model.ts:696:8) at /app/front/tests/006-stdcm.spec.ts:131:21

2) [webkit] › 006-stdcm.spec.ts:139:7 › Verify train schedule elements and filters › Launch simulation with and without capacity for towed rolling stock 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/006-stdcm.spec.ts:161:5

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

3) [webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result Error: page.waitForLoadState: Test timeout of 270000ms exceeded. at pages/op-timetable-page-model.ts:203 201 | 202 | for (let currentTrainIndex = 0; currentTrainIndex < trainCount; currentTrainIndex += 1) { > 203 | await this.page.waitForLoadState('networkidle'); | ^ 204 | await this.waitForSimulationResults(); 205 | const trainButton = OperationalStudiesTimetablePage.getTrainButton( 206 | this.timetableTrains.nth(currentTrainIndex) at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:203:23) at /app/front/tests/008-train-schedule.spec.ts:57:5

3) [webkit] › 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.

3) [webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: page.waitForLoadState: Test timeout of 270000ms exceeded. at pages/op-timetable-page-model.ts:97 95 | // Verify that simulation results are displayed 96 | async verifySimulationResultsVisibility(): Promise<void> { > 97 | await this.page.waitForLoadState('networkidle'); | ^ 98 | 99 | const simulationResultsLocators = [ 100 | // TODO: remove this commented code when the design of simationBar has been changed at OperationalStudiesTimetablePage.verifySimulationResultsVisibility (/app/front/tests/pages/op-timetable-page-model.ts:97:21) at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:209:18) at /app/front/tests/008-train-schedule.spec.ts:57:5

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 1.7m

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

[webkit] › 011-op-times-and-stops-tab.spec.ts took 33.6s

[chromium] › 009-rollingstock-editor.spec.ts took 30.5s

[webkit] › 010-op-route-tab.spec.ts took 25.5s