build #12029
build.yml
on: merge_group
Matrix: build
check_generated_railjson_sync
23s
check_railjson_generator
1m 52s
check_commits
10s
Check final newline
10s
check_integration_tests
1m 26s
check_osrd_schema
40s
check_toml
5s
check_infra_schema_sync
18s
check_reuse_compliance
9s
check_front_rtk_sync
1m 50s
check_core
4m 8s
check_editoast_tests
4m 5s
check_editoast_lints
4m 50s
check_editoast_openapi
1m 23s
check_gateway
1m 59s
check_osrdyne
2m 40s
check_front
2m 58s
integration_tests
12m 27s
Annotations
5 errors, 13 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
|
[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
|
[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
3) [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] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study:
tests/010-op-route-tab.spec.ts#L1
4) [webkit] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study
Test timeout of 270000ms exceeded.
|
[webkit] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study:
tests/pages/operational-studies-page-model.ts#L260
4) [webkit] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study
Error: locator.waitFor: Test timeout of 270000ms exceeded.
Call log:
- waiting for getByTestId('missing-params-info') to be visible
at pages/operational-studies-page-model.ts:260
258 | ''
259 | );
> 260 | await this.missingParamMessage.waitFor();
| ^
261 | const actualMessage = await this.missingParamMessage.innerText();
262 | expect(actualMessage).toContain(expectedMessage);
263 | }
at OperationalStudiesPage.clickOnDeleteOPButtons (/app/tests/pages/operational-studies-page-model.ts:260:36)
at /app/tests/010-op-route-tab.spec.ts:141:5
|
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 (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 (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/
|
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 (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_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_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/
|
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/
|
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] › 009-rollingstock-editor.spec.ts#L1
[chromium] › 009-rollingstock-editor.spec.ts took 35.1s
|
🎭 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
[webkit] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
[webkit] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study
3 skipped
79 passed (8.9m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
integration-container-logs
Expired
|
222 KB |
|
integration-videos
Expired
|
12.7 MB |
|