Skip to content

editoast: moved utility functions to helpers.rs #10978

editoast: moved utility functions to helpers.rs

editoast: moved utility functions to helpers.rs #10978

Triggered via pull request September 16, 2024 08:47
Status Success
Total duration 15m 16s
Artifacts 2

build.yml

on: pull_request
Matrix: build
check_generated_railjson_sync
26s
check_generated_railjson_sync
check_railjson_generator
1m 50s
check_railjson_generator
check_commits
8s
check_commits
Check final newline
7s
Check final newline
check_integration_tests
1m 24s
check_integration_tests
check_osrd_schema
42s
check_osrd_schema
check_toml
4s
check_toml
check_infra_schema_sync
25s
check_infra_schema_sync
check_reuse_compliance
10s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 16 warnings, and 1 notice
[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
1) [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/003-study-management.spec.ts#L67
1) [firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Error: page.waitForURL: Test timeout of 60000ms exceeded. =========================== logs =========================== waiting for navigation to "**/studies/*" until "load" ============================================================ 65 | const createButton = homePage.page.getByTestId('createStudy'); 66 | await createButton.click(); > 67 | await homePage.page.waitForURL('**/studies/*'); | ^ 68 | expect(await studyPage.getStudyName.textContent()).toContain(studyName); 69 | expect(await studyPage.getStudyDescription.textContent()).toContain(studyData.description); 70 | expect(await studyPage.getStudyType.textContent()).toContain(studyData.type); at /app/tests/003-study-management.spec.ts:67:25
[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
2) [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#L36
3) [webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('add-study-button') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('add-study-button') 34 | await page.goto(`/operational-studies/projects/${project.id}`); 35 | > 36 | await expect(studyPage.getAddStudyBtn).toBeVisible(); | ^ 37 | await studyPage.openStudyCreationModal(); 38 | 39 | const studyName = `${studyData.name} ${uuidv4()}`; at /app/tests/003-study-management.spec.ts:36:44
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 (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 (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_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_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_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: [firefox] › 008-train-schedule.spec.ts#L1
[firefox] › 008-train-schedule.spec.ts took 20.8s
Slow Test: [webkit] › 004-scenario-management.spec.ts#L1
[webkit] › 004-scenario-management.spec.ts took 16.8s
Slow Test: [webkit] › 001-home-page.spec.ts#L1
[webkit] › 001-home-page.spec.ts took 16.2s
Slow Test: [chromium] › 005-operational-studies.spec.ts#L1
[chromium] › 005-operational-studies.spec.ts took 15.3s
🎭 Playwright Run Summary
3 flaky [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 83 passed (6.5m)

Artifacts

Produced during runtime
Name Size
integration-container-logs
237 KB
integration-videos
10.6 MB