front: fix stdcm consist warning #17741
build.yml
on: push
Matrix: Build
Check dockerfiles
8s
Check scripts
5s
Check generated railjson sync
25s
Check railjson generator
1m 50s
Check commits
7s
Check final newline
8s
Check integration tests
1m 19s
Check osrd schema
40s
Check toml
5s
Check infra schema sync
19s
Check reuse compliance
9s
Check front rtk sync
1m 17s
Check core
4m 3s
Check editoast tests
6m 50s
Check editoast lints
8m 36s
Check editoast openapi
44s
Check gateway
3m 22s
Check osrdyne
3m 36s
Check front
3m 18s
Integration tests
1m 5s
End to end tests
22m 42s
Annotations
10 errors, 31 warnings, and 1 notice
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result:
tests/008-train-schedule.spec.ts#L1
1) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Test timeout of 270000ms exceeded.
|
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result:
tests/pages/op-timetable-page-model.ts#L203
1) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Error: page.waitForLoadState: Test timeout of 270000ms exceeded.
at pages/op-timetable-page-model.ts:203
201 |
202 | for (let currentTrainIndex = 0; currentTrainIndex < trainCount; currentTrainIndex += 1) {
> 203 | await this.page.waitForLoadState('networkidle');
| ^
204 | await this.waitForSimulationResults();
205 | const trainButton = OperationalStudiesTimetablePage.getTrainButton(
206 | this.timetableTrains.nth(currentTrainIndex)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:203:23)
at /app/front/tests/008-train-schedule.spec.ts:57:5
|
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result:
tests/008-train-schedule.spec.ts#L1
1) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 270000ms exceeded.
|
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result:
tests/pages/op-timetable-page-model.ts#L203
1) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: page.waitForLoadState: Test timeout of 270000ms exceeded.
at pages/op-timetable-page-model.ts:203
201 |
202 | for (let currentTrainIndex = 0; currentTrainIndex < trainCount; currentTrainIndex += 1) {
> 203 | await this.page.waitForLoadState('networkidle');
| ^
204 | await this.waitForSimulationResults();
205 | const trainButton = OperationalStudiesTimetablePage.getTrainButton(
206 | this.timetableTrains.nth(currentTrainIndex)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:203:23)
at /app/front/tests/008-train-schedule.spec.ts:57:5
|
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result:
tests/008-train-schedule.spec.ts#L1
1) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 270000ms exceeded.
|
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result:
tests/pages/op-timetable-page-model.ts#L203
1) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: page.waitForLoadState: Test timeout of 270000ms exceeded.
at pages/op-timetable-page-model.ts:203
201 |
202 | for (let currentTrainIndex = 0; currentTrainIndex < trainCount; currentTrainIndex += 1) {
> 203 | await this.page.waitForLoadState('networkidle');
| ^
204 | await this.waitForSimulationResults();
205 | const trainButton = OperationalStudiesTimetablePage.getTrainButton(
206 | this.timetableTrains.nth(currentTrainIndex)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:203:23)
at /app/front/tests/008-train-schedule.spec.ts:57:5
|
[webkit] › 006-stdcm.spec.ts:102:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet:
tests/pages/stdcm-page-model.ts#L696
2) [webkit] › 006-stdcm.spec.ts:102:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
Error: Timeout 90000ms exceeded while waiting on the predicate
at pages/stdcm-page-model.ts:696
694 | await download.saveAs(downloadPath);
695 | logger.info(`The PDF was successfully downloaded to: ${downloadPath}`);
> 696 | }).toPass({
| ^
697 | timeout: EXPECT_TO_PASS_TIMEOUT,
698 | });
699 | }
at STDCMPage.downloadSimulation (/app/front/tests/pages/stdcm-page-model.ts:696:8)
at /app/front/tests/006-stdcm.spec.ts:131:21
|
[webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result:
tests/008-train-schedule.spec.ts#L1
3) [webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Test timeout of 270000ms exceeded.
|
[webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result:
tests/pages/op-timetable-page-model.ts#L203
3) [webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Error: page.waitForLoadState: Test timeout of 270000ms exceeded.
at pages/op-timetable-page-model.ts:203
201 |
202 | for (let currentTrainIndex = 0; currentTrainIndex < trainCount; currentTrainIndex += 1) {
> 203 | await this.page.waitForLoadState('networkidle');
| ^
204 | await this.waitForSimulationResults();
205 | const trainButton = OperationalStudiesTimetablePage.getTrainButton(
206 | this.timetableTrains.nth(currentTrainIndex)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:203:23)
at /app/front/tests/008-train-schedule.spec.ts:57:5
|
End to end tests
Process completed with exit code 1.
|
Check scripts
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check toml
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check commits
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check dockerfiles
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check final newline
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check reuse compliance
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build (osrdyne, osrdyne-test)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check infra schema sync
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check generated railjson sync
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build (core-build, core)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build (editoast, editoast-test)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check osrd schema
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check integration tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check railjson generator
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build (front-build, front-tests, front-devel, front-nginx)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build (gateway-test, gateway-standalone, gateway-front)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check editoast openapi
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Integration tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check front rtk sync
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check front
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check gateway
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check osrdyne
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check core
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check editoast tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Check editoast lints
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
End to end tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Slow Test:
[chromium] › 012-op-simulation-settings-tab.spec.ts#L1
[chromium] › 012-op-simulation-settings-tab.spec.ts took 1.6m
|
Slow Test:
[chromium] › 006-stdcm.spec.ts#L1
[chromium] › 006-stdcm.spec.ts took 1.4m
|
Slow Test:
[firefox] › 006-stdcm.spec.ts#L1
[firefox] › 006-stdcm.spec.ts took 1.2m
|
Slow Test:
[webkit] › 009-rollingstock-editor.spec.ts#L1
[webkit] › 009-rollingstock-editor.spec.ts took 1.0m
|
Slow Test:
[firefox] › 012-op-simulation-settings-tab.spec.ts#L1
[firefox] › 012-op-simulation-settings-tab.spec.ts took 53.9s
|
🎭 Playwright Run Summary
1 failed
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
2 flaky
[webkit] › 006-stdcm.spec.ts:102:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
[webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
110 passed (21.1m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
e2e-container-logs
|
496 KB |
|
integration-container-logs
|
29.8 KB |
|
integration-videos
|
28.2 MB |
|