1) [chromium] › 004-scenario-management.spec.ts:97:7 › Validate the Scenario creation workflow › Delete a scenario Error: Timed out 10000ms waiting for expect(locator).not.toBeVisible() Locator: locator('#modal-content').getByTestId('delete-scenario') Expected: not visible Received: visible Call log: - expect.not.toBeVisible with timeout 10000ms - waiting for locator('#modal-content').getByTestId('delete-scenario') - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" - locator resolved to <button type="button" data-testid="delete-scenario" clas…>…</button> - unexpected value "visible" at pages/scenario-page-model.ts:165 163 | async deleteScenario() { 164 | await this.scenarioConfirmDeleteButton.click(); > 165 | await expect(this.scenarioConfirmDeleteButton).not.toBeVisible(); | ^ 166 | await this.page.waitForURL('**/studies/*'); 167 | } 168 | } at ScenarioPage.deleteScenario (/app/front/tests/pages/scenario-page-model.ts:165:56) at /app/front/tests/004-scenario-management.spec.ts:109:5

2) [chromium] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet Error: Timed out 10000ms waiting for expect(locator).toBeEnabled() Locator: getByTestId('launch-simulation-button') Expected: enabled Received: disabled Call log: - expect.toBeEnabled with timeout 10000ms - waiting for getByTestId('launch-simulation-button') - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" Call Log: - Timeout 90000ms exceeded while waiting on the predicate at pages/stdcm-page-model.ts:616 614 | await expect(this.mapResultContainer).toBeVisible(); 615 | } > 616 | }).toPass({ | ^ 617 | timeout: EXPECT_TO_PASS_TIMEOUT, 618 | }); 619 | } at STDCMPage.launchSimulation (/app/front/tests/pages/stdcm-page-model.ts:616:8) at /app/front/tests/006-stdcm.spec.ts:117:21

3) [webkit] › 006-stdcm.spec.ts:97: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:685 683 | await download.saveAs(downloadPath); 684 | logger.info(`The PDF was successfully downloaded to: ${downloadPath}`); > 685 | }).toPass({ | ^ 686 | timeout: EXPECT_TO_PASS_TIMEOUT, 687 | }); 688 | } at STDCMPage.downloadSimulation (/app/front/tests/pages/stdcm-page-model.ts:685:8) at /app/front/tests/006-stdcm.spec.ts:126:21

4) [webkit] › 006-stdcm.spec.ts:134:7 › Verify train schedule elements and filters › Launch simulation with and without capacity for towed rolling stock Error: expect(received).toEqual(expected) // deep equality Expected: "Pas de capacité" Received: "Simulation n°2" at pages/stdcm-page-model.ts:726 724 | const actualSimulationName = 725 | await this.getSimulationNameLocator(simulationNumber).textContent(); > 726 | expect(actualSimulationName).toEqual(expectedSimulationName); | ^ 727 | 728 | // Determine expected length and duration 729 | const expectedLengthAndDuration = isResultTableVisible at STDCMPage.verifySimulationDetails (/app/front/tests/pages/stdcm-page-model.ts:726:34) at /app/front/tests/006-stdcm.spec.ts:164: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

[firefox] › 009-rollingstock-editor.spec.ts took 35.5s

[firefox] › 008-train-schedule.spec.ts took 22.5s

[chromium] › 005-operational-studies.spec.ts took 19.7s

[firefox] › 010-op-route-tab.spec.ts took 18.1s