editoast: work schedule projection endpoint #11016
build.yml
on: pull_request
Matrix: build
check_generated_railjson_sync
26s
check_railjson_generator
1m 48s
check_commits
8s
Check final newline
13s
check_integration_tests
1m 25s
check_osrd_schema
45s
check_toml
8s
check_infra_schema_sync
24s
check_reuse_compliance
8s
check_front_rtk_sync
1m 55s
check_core
4m 4s
check_editoast_tests
4m 19s
check_editoast_lints
5m 6s
check_editoast_openapi
1m 14s
check_gateway
2m 12s
check_osrdyne
2m 43s
check_front
2m 46s
integration_tests
9m 5s
Annotations
7 errors, 12 warnings, and 1 notice
check_commits
Process completed with exit code 1.
|
[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
|
[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
2) [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
|
[firefox] › 010-op-route-tab.spec.ts:67: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
3) [firefox] › 010-op-route-tab.spec.ts:67: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:89:5
|
[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] › 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
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
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/api-setup.ts#L46
4) [webkit] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
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
|
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/
|
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/
|
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 (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_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/
|
🎭 Playwright Run Summary
4 flaky
[chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
[firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
[firefox] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study
[webkit] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
82 passed (4.7m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
integration-container-logs
|
220 KB |
|
integration-videos
|
9.98 MB |
|