Process completed with exit code 1.

1) [chromium] › 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) [chromium] › 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

1) [chromium] › 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) [chromium] › 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: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

2) [firefox] › 012-op-simulation-settings-tab.spec.ts:134:7 › Simulation Settings Tab Verification › Activate electrical profiles Error: Screenshot comparison failed: 56883 pixels (ratio 0.05 of all image pixels) are different. Expected: /app/front/tests/012-op-simulation-settings-tab.spec.ts-snapshots/SpeedSpaceChart-ElectricalProfileDisabled-firefox-linux.png Received: /app/front/test-results/012-op-simulation-settings-37d1f-ctivate-electrical-profiles-firefox/SpeedSpaceChart-ElectricalProfileDisabled-actual.png Diff: /app/front/test-results/012-op-simulation-settings-37d1f-ctivate-electrical-profiles-firefox/SpeedSpaceChart-ElectricalProfileDisabled-diff.png Call log: - page._expectScreenshot with timeout 10000ms - verifying given screenshot expectation - waiting for locator('#container-SpeedSpaceChart > div[tabindex="0"]') - locator resolved to <div tabindex="0">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 56883 pixels (ratio 0.05 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('#container-SpeedSpaceChart > div[tabindex="0"]') - locator resolved to <div tabindex="0">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 56883 pixels (ratio 0.05 of all image pixels) are different. 202 | async () => { 203 | await simulationResultPage.selectAllSpeedSpaceChartCheckboxes(); > 204 | await expect(simulationResultPage.speedSpaceChartTabindexElement).toHaveScreenshot( | ^ 205 | 'SpeedSpaceChart-ElectricalProfileDisabled.png' 206 | ); 207 | }, at currentBrowser (/app/front/tests/012-op-simulation-settings-tab.spec.ts:204:75) at performOnSpecificOSAndBrowser (/app/front/tests/utils/index.ts:186:5) at /app/front/tests/012-op-simulation-settings-tab.spec.ts:201:5

3) [firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code Test timeout of 270000ms exceeded.

3) [firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code Error: locator.click: Test timeout of 270000ms exceeded. Call log: - waiting for getByTestId('close-toast-button').first() - locator resolved to <button type="button" class="ml-2 close" data-testid="cl…>…</button> - attempting click action - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #2 - waiting 20ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #3 - waiting 100ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #4 - waiting 100ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #5 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #6 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #7 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #8 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #9 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #10 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #11 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #12 - waiting 500ms - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying at pages/common-page-model.ts:47 45 | async closeToastNotification(): Promise<void> { 46 | const closeToastElements = await this.closeToastButton.all(); > 47 | await Promise.all(closeToastElements.map((closeToastElement) => closeToastElement.click())); | ^ 48 | } 49 | } 50 | at map (/app/front/tests/pages/common-page-model.ts:47:87) at OperationalStudiesTimetablePage.closeToastNotification (/app/front/tests/pages/common-page-model.ts:47:42) at OperationalStudiesTimetablePage.clickOnEditTrainSchedule (/app/front/tests/pages/op-timetable-page-model.ts:226:5) at /app/front/tests/012-op-simulation-settings-tab.spec.ts:276:5

4) [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

5) [webkit] › 008-train-schedule.spec.ts:61:7 › Verify train schedule elements and filters › Filtering imported trains Test timeout of 270000ms exceeded.

5) [webkit] › 008-train-schedule.spec.ts:61:7 › Verify train schedule elements and filters › Filtering imported trains Error: page.waitForLoadState: Test timeout of 270000ms exceeded. at pages/op-timetable-page-model.ts:154 152 | // Verify that the imported train number is correct 153 | async verifyTrainCount(trainCount: number): Promise<void> { > 154 | await this.page.waitForLoadState('networkidle'); | ^ 155 | await expect(this.timetableTrains).toHaveCount(trainCount); 156 | } 157 | at OperationalStudiesTimetablePage.verifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:154:21) at OperationalStudiesTimetablePage.filterHonoredAndVerifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:195:16) at /app/front/tests/008-train-schedule.spec.ts:72: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

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.8m

[chromium] › 012-op-simulation-settings-tab.spec.ts took 1.5m

[chromium] › 006-stdcm.spec.ts took 1.4m

[firefox] › 006-stdcm.spec.ts took 1.2m

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