front: add stop type in stdcm #10976
build.yml
on: pull_request
Matrix: build
check_generated_railjson_sync
23s
check_railjson_generator
1m 53s
check_commits
7s
Check final newline
9s
check_integration_tests
1m 24s
check_osrd_schema
46s
check_toml
6s
check_infra_schema_sync
18s
check_reuse_compliance
11s
check_front_rtk_sync
1m 31s
check_core
4m 10s
check_editoast_tests
4m 22s
check_editoast_lints
5m 1s
check_editoast_openapi
1m 11s
check_gateway
2m 11s
check_osrdyne
2m 38s
check_front
1m 12s
integration_tests
10m 32s
Annotations
8 errors, 16 warnings, and 1 notice
check_commits
Process completed with exit code 1.
|
check_front
Process completed with exit code 1.
|
[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
1) [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
1) [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
2) [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
2) [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:125: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
3) [firefox] › 010-op-route-tab.spec.ts:125: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 60000ms exceeded.
|
[firefox] › 010-op-route-tab.spec.ts:125: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#L255
3) [firefox] › 010-op-route-tab.spec.ts:125: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 60000ms exceeded.
Call log:
- waiting for getByTestId('missing-params-info') to be visible
at pages/operational-studies-page-model.ts:255
253 | ''
254 | );
> 255 | await this.missingParamMessage.waitFor();
| ^
256 | const actualMessage = await this.missingParamMessage.innerText();
257 | expect(actualMessage).toContain(expectedMessage);
258 | }
at OperationalStudiesPage.clickOnDeleteOPButtons (/app/tests/pages/operational-studies-page-model.ts:255:36)
at /app/tests/010-op-route-tab.spec.ts:155: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_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 44.8s
|
Slow Test:
[webkit] › 003-study-management.spec.ts#L1
[webkit] › 003-study-management.spec.ts took 27.8s
|
Slow Test:
[webkit] › 002-project-management.spec.ts#L1
[webkit] › 002-project-management.spec.ts took 20.4s
|
Slow Test:
[firefox] › 008-train-schedule.spec.ts#L1
[firefox] › 008-train-schedule.spec.ts took 18.8s
|
Slow Test:
[webkit] › 006-stdcm-page.spec.ts#L1
[webkit] › 006-stdcm-page.spec.ts took 15.7s
|
🎭 Playwright Run Summary
3 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:125:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study
83 passed (7.1m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
integration-container-logs
|
237 KB |
|
integration-videos
|
11.5 MB |
|