1) [firefox] › 011-op-times-and-stops-tab.spec.ts:115:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables Error: Failed to create scenario: 500 Internal Server Error at utils/api-setup.ts:67 65 | if (response.ok()) return; 66 | > 67 | throw new Error(`${errorMessage}: ${response.status()} ${response.statusText()}`); | ^ 68 | } 69 | 70 | /** at handleErrorResponse (/app/front/tests/utils/api-setup.ts:67:9) at postApiRequest (/app/front/tests/utils/api-setup.ts:87:3) at createScenario (/app/front/tests/utils/scenario.ts:46:30) at /app/front/tests/011-op-times-and-stops-tab.spec.ts:84:39

1) [firefox] › 011-op-times-and-stops-tab.spec.ts:115:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables TypeError: Cannot read properties of undefined (reading 'id') 110 | 111 | test.afterEach('Delete the created scenario', async () => { > 112 | await deleteScenario(project.id, study.id, scenario.name); | ^ 113 | }); 114 | 115 | test('should correctly set and display times and stops tables', async ({ page }) => { at /app/front/tests/011-op-times-and-stops-tab.spec.ts:112:34

2) [webkit] › 006-stdcm.spec.ts:70:7 › Verify train schedule elements and filters › Launch STDCM simulation with all stops 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:92: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

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

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

[chromium] › 007-op-rollingstock-tab.spec.ts took 16.6s