Skip to content

build

build #12740

Triggered via merge group October 11, 2024 09:17
Status Success
Total duration 37m 11s
Artifacts 2

build.yml

on: merge_group
Matrix: build
check_generated_railjson_sync
26s
check_generated_railjson_sync
check_railjson_generator
1m 48s
check_railjson_generator
check_commits
8s
check_commits
Check final newline
10s
Check final newline
check_integration_tests
1m 23s
check_integration_tests
check_osrd_schema
39s
check_osrd_schema
check_toml
4s
check_toml
check_infra_schema_sync
15s
check_infra_schema_sync
check_reuse_compliance
8s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 14 warnings, and 1 notice
[chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario: tests/utils/scenario.ts#L27
1) [chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:27 25 | // Create a new scenario with a unique name 26 | const scenario = await postApiRequest( > 27 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 28 | { 29 | ...scenarioData, 30 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:27:50) at /app/tests/004-scenario-management.spec.ts:17:35
[chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario: tests/utils/api-setup.ts#L46
1) [chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: Cannot read properties of undefined (reading 'find') at utils/api-setup.ts:46 44 | 45 | const findOneInResults = <T extends { name: string }>(results: T[], name: string) => > 46 | results.find((result) => result.name.includes(name)); | ^ 47 | 48 | export const getInfra = async () => { 49 | const { results } = await getApiRequest(`/api/infra/`); at findOneInResults (/app/tests/utils/api-setup.ts:46:11) at getStudy (/app/tests/utils/api-setup.ts:62:17) at setupScenario (/app/tests/utils/scenario.ts:22:17) at /app/tests/004-scenario-management.spec.ts:17:35
[chromium] › 004-scenario-management.spec.ts:56:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario: tests/004-scenario-management.spec.ts#L1
2) [chromium] › 004-scenario-management.spec.ts:56:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario Test timeout of 90000ms exceeded.
[chromium] › 004-scenario-management.spec.ts:56:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario: tests/004-scenario-management.spec.ts#L77
2) [chromium] › 004-scenario-management.spec.ts:56:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario Error: locator.textContent: Test timeout of 90000ms exceeded. Call log: - waiting for getByTestId('scenario-card-scenario_test_e2e 2c599263-d015-4762-9dcf-e798a6a768e5').locator('.scenario-card-tags') 75 | await page.goto(`/operational-studies/projects/${project.id}/studies/${study.id}`); 76 | > 77 | expect(await scenarioPage.getScenarioTags(scenarioName).textContent()).toContain( | ^ 78 | `${scenarioData.tags.join('')}update-tag` 79 | ); 80 | at /app/tests/004-scenario-management.spec.ts:77:61
[firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario: tests/utils/scenario.ts#L27
3) [firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:27 25 | // Create a new scenario with a unique name 26 | const scenario = await postApiRequest( > 27 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 28 | { 29 | ...scenarioData, 30 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:27:50) at /app/tests/004-scenario-management.spec.ts:17:35
[webkit] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario: tests/utils/scenario.ts#L27
4) [webkit] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:27 25 | // Create a new scenario with a unique name 26 | const scenario = await postApiRequest( > 27 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 28 | { 29 | ...scenarioData, 30 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:27:50) at /app/tests/004-scenario-management.spec.ts:17:35
[webkit] › 011-op-times-and-stops-tab.spec.ts:166:7 › Times and Stops Tab Verification › should correctly update and clear input table row: tests/pages/operational-studies-page-model.ts#L400
5) [webkit] › 011-op-times-and-stops-tab.spec.ts:166:7 › Times and Stops Tab Verification › should correctly update and clear input table row Error: locator.innerText: Error: strict mode violation: getByTestId('selected-rolling-stock-info') resolved to 2 elements: 1) <span class="rollingstock-info-end" data-testid="selec…>dual-mode_rollingstock_test_e2e</span> aka getByTestId('rollingstock-dual-mode_rollingstock_test_e2e').locator('div').filter({ hasText: 'dual-modedual-modedual-' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>dual-mode_rollingstock_test_e2e</span> aka getByTestId('rollingstock-selector') Call log: - waiting for getByTestId('selected-rolling-stock-info') at pages/operational-studies-page-model.ts:400 398 | await electricRollingstockCard.click(); 399 | await electricRollingstockCard.locator('button').click(); > 400 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 401 | rollingStockName 402 | ); 403 | } at OperationalStudiesPage.selectRollingStock (/app/tests/pages/operational-studies-page-model.ts:400:67) at /app/tests/011-op-times-and-stops-tab.spec.ts:180:5
build (front-build, front-tests, front-devel, front-nginx)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_railjson_generator
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/
build (core-build, core)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (osrdyne, osrdyne-test)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (gateway-test, gateway-standalone, gateway-front)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (editoast, editoast-test)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_front
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/
check_osrdyne
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/
check_gateway
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/
check_core
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/
check_editoast_tests
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/
integration_tests
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/
Slow Test: [chromium] › 008-train-schedule.spec.ts#L1
[chromium] › 008-train-schedule.spec.ts took 31.0s
Slow Test: [chromium] › 009-rollingstock-editor.spec.ts#L1
[chromium] › 009-rollingstock-editor.spec.ts took 28.1s
🎭 Playwright Run Summary
5 flaky [chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario [chromium] › 004-scenario-management.spec.ts:56:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario [firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario [webkit] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario [webkit] › 011-op-times-and-stops-tab.spec.ts:166:7 › Times and Stops Tab Verification › should correctly update and clear input table row 3 skipped 84 passed (6.1m)

Artifacts

Produced during runtime
Name Size
integration-container-logs
242 KB
integration-videos
16.8 MB