Skip to content

build

build #10888

Triggered via merge group September 12, 2024 09:19
Status Failure
Total duration 21m 52s
Artifacts 2

build.yml

on: merge_group
Matrix: build
check_generated_railjson_sync
21s
check_generated_railjson_sync
check_railjson_generator
1m 51s
check_railjson_generator
check_commits
8s
check_commits
Check final newline
7s
Check final newline
check_integration_tests
1m 21s
check_integration_tests
check_osrd_schema
53s
check_osrd_schema
check_toml
5s
check_toml
check_infra_schema_sync
15s
check_infra_schema_sync
check_reuse_compliance
11s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 15 warnings, and 1 notice
[chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study: tests/pages/operational-studies-page-model.ts#L304
1) [chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Error: Timed out 10000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') Expected string: "Mid_East_station" Received string: "" Call log: - expect.toHaveText with timeout 10000ms - waiting for getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') at pages/operational-studies-page-model.ts:304 302 | expectedUic: string 303 | ) { > 304 | await expect(OperationalStudiesPage.getWaypointDroppedNameLocator(droppedWaypoint)).toHaveText( | ^ 305 | expectedName 306 | ); 307 | await expect(OperationalStudiesPage.getWaypointDroppedChLocator(droppedWaypoint)).toHaveText( at Function.validateAddedWaypoint (/app/tests/pages/operational-studies-page-model.ts:304:89) at OperationalStudiesPage.addNewWaypoints (/app/tests/pages/operational-studies-page-model.ts:351:36) at /app/tests/010-op-route-tab.spec.ts:103:5
[chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study: tests/010-op-route-tab.spec.ts#L29
1) [chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: Cannot read properties of undefined (reading 'id') 27 | test.beforeEach(async ({ page }) => { 28 | timetableResult = await postApiRequest(`/api/timetable/`); > 29 | scenario = await postApiRequest(`/api/projects/${project.id}/studies/${study.id}/scenarios/`, { | ^ 30 | ...scenarioData, 31 | name: `${scenarioData.name} ${uuidv4()}`, 32 | study_id: study.id, at /app/tests/010-op-route-tab.spec.ts:29:80
[chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study: tests/010-op-route-tab.spec.ts#L29
1) [chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: Cannot read properties of undefined (reading 'id') 27 | test.beforeEach(async ({ page }) => { 28 | timetableResult = await postApiRequest(`/api/timetable/`); > 29 | scenario = await postApiRequest(`/api/projects/${project.id}/studies/${study.id}/scenarios/`, { | ^ 30 | ...scenarioData, 31 | name: `${scenarioData.name} ${uuidv4()}`, 32 | study_id: study.id, at /app/tests/010-op-route-tab.spec.ts:29:80
[chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study: tests/010-op-route-tab.spec.ts#L29
1) [chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: Cannot read properties of undefined (reading 'id') 27 | test.beforeEach(async ({ page }) => { 28 | timetableResult = await postApiRequest(`/api/timetable/`); > 29 | scenario = await postApiRequest(`/api/projects/${project.id}/studies/${study.id}/scenarios/`, { | ^ 30 | ...scenarioData, 31 | name: `${scenarioData.name} ${uuidv4()}`, 32 | study_id: study.id, at /app/tests/010-op-route-tab.spec.ts:29:80
[chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/003-study-management.spec.ts#L1
2) [chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Test timeout of 60000ms exceeded.
[chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/pages/study-page-model.ts#L110
2) [chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Error: locator.click: Test timeout of 60000ms exceeded. Call log: - waiting for getByTestId('add-study-button') - locator resolved to <div tabindex="0" role="button" class="study-card emp…>…</div> - attempting click action - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying at pages/study-page-model.ts:110 108 | 109 | async openStudyCreationModal() { > 110 | await this.getAddStudyBtn.click(); | ^ 111 | } 112 | 113 | async setStudyName(name: string) { at StudyPage.openStudyCreationModal (/app/tests/pages/study-page-model.ts:110:31) at /app/tests/003-study-management.spec.ts:37:21
[firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/003-study-management.spec.ts#L1
3) [firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Test timeout of 60000ms exceeded.
[firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/pages/study-page-model.ts#L110
3) [firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Error: locator.click: Test timeout of 60000ms exceeded. Call log: - waiting for getByTestId('add-study-button') at pages/study-page-model.ts:110 108 | 109 | async openStudyCreationModal() { > 110 | await this.getAddStudyBtn.click(); | ^ 111 | } 112 | 113 | async setStudyName(name: string) { at StudyPage.openStudyCreationModal (/app/tests/pages/study-page-model.ts:110:31) at /app/tests/003-study-management.spec.ts:37:21
[firefox] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study: tests/pages/operational-studies-page-model.ts#L304
4) [firefox] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study Error: Timed out 10000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') Expected string: "Mid_East_station" Received string: "" Call log: - expect.toHaveText with timeout 10000ms - waiting for getByTestId('dropped-via-info').nth(1).getByTestId('via-dropped-name') at pages/operational-studies-page-model.ts:304 302 | expectedUic: string 303 | ) { > 304 | await expect(OperationalStudiesPage.getWaypointDroppedNameLocator(droppedWaypoint)).toHaveText( | ^ 305 | expectedName 306 | ); 307 | await expect(OperationalStudiesPage.getWaypointDroppedChLocator(droppedWaypoint)).toHaveText( at Function.validateAddedWaypoint (/app/tests/pages/operational-studies-page-model.ts:304:89) at OperationalStudiesPage.addNewWaypoints (/app/tests/pages/operational-studies-page-model.ts:351:36) at /app/tests/010-op-route-tab.spec.ts:103:5
[webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/003-study-management.spec.ts#L1
5) [webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Test timeout of 60000ms exceeded.
🎭 Playwright Run Summary
1 failed [chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study 4 flaky [chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study [firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study [firefox] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study [webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study 81 passed (7.2m)
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 (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/
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/
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 (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_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_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_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 43.4s
Slow Test: [firefox] › 008-train-schedule.spec.ts#L1
[firefox] › 008-train-schedule.spec.ts took 20.6s
Slow Test: [webkit] › 004-scenario-management.spec.ts#L1
[webkit] › 004-scenario-management.spec.ts took 16.4s

Artifacts

Produced during runtime
Name Size
integration-container-logs
283 KB
integration-videos
13.2 MB