1) [chromium] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:29 27 | // Create a new scenario with a unique name 28 | const scenario = await postApiRequest( > 29 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 30 | { 31 | ...scenarioData, 32 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:29:50) at /app/tests/004-scenario-management.spec.ts:17:35

2) [firefox] › 001-home-page.spec.ts:22:7 › Home page OSRD › should display links in the home page Error: expect(locator).toHaveText(expected) Locator: locator('h5') - Expected - 5 + Received + 5 Array [ - "Études d'exploitation", - "Sillons de dernière minute", - "Éditeur d'infrastructure", - "Éditeur de matériel roulant", - "Cartographie", + "operationalStudies", + "stdcm", + "editor", + "rollingStockEditor", + "map", ] Call log: - expect.toHaveText with timeout 10000ms - waiting for locator('h5') - locator resolved to 5 elements - locator resolved to 5 elements at pages/home-page-model.ts:79 77 | // Assert that the expected links are displayed on the page 78 | async getDisplayLinks() { > 79 | expect(this.getLinks).toHaveText([ | ^ 80 | this.getTranslations('operationalStudies'), 81 | this.getTranslations('stdcm'), 82 | this.getTranslations('editor'), at HomePage.getDisplayLinks (/app/tests/pages/home-page-model.ts:79:27) at /app/tests/001-home-page.spec.ts:23:20

3) [firefox] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:29 27 | // Create a new scenario with a unique name 28 | const scenario = await postApiRequest( > 29 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 30 | { 31 | ...scenarioData, 32 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:29:50) at /app/tests/004-scenario-management.spec.ts:17:35

4) [webkit] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:29 27 | // Create a new scenario with a unique name 28 | const scenario = await postApiRequest( > 29 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 30 | { 31 | ...scenarioData, 32 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:29:50) at /app/tests/004-scenario-management.spec.ts:17:35

4) [webkit] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:29 27 | // Create a new scenario with a unique name 28 | const scenario = await postApiRequest( > 29 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 30 | { 31 | ...scenarioData, 32 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:29:50) at /app/tests/004-scenario-management.spec.ts:17:35

The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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