front: display only trains around stdcm result #17867
build.yml
on: pull_request
Matrix: Build
Check dockerfiles
13s
Check scripts
6s
Check generated railjson sync
25s
Check railjson generator
1m 50s
Check commits
8s
Check final newline
8s
Check integration tests
1m 23s
Check osrd schema
39s
Check toml
9s
Check infra schema sync
16s
Check reuse compliance
13s
Check front rtk sync
1m 13s
Check core
4m 7s
Check editoast tests
7m 14s
Check editoast lints
8m 46s
Check editoast openapi
46s
Check gateway
3m 30s
Check osrdyne
3m 41s
Check front
3m 14s
Integration tests
1m 2s
End to end tests
19m 11s
Annotations
7 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
|
[firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code:
tests/012-op-simulation-settings-tab.spec.ts#L1
2) [firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code
Test timeout of 270000ms exceeded.
|
[firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code:
tests/pages/common-page-model.ts#L47
2) [firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code
Error: locator.click: Test timeout of 270000ms exceeded.
Call log:
- waiting for getByTestId('close-toast-button').nth(1)
- locator resolved to <button type="button" class="ml-2 close" data-testid="cl…>…</button>
- attempting click action
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- element was detached from the DOM, retrying
at pages/common-page-model.ts:47
45 | async closeToastNotification(): Promise<void> {
46 | const closeToastElements = await this.closeToastButton.all();
> 47 | await Promise.all(closeToastElements.map((closeToastElement) => closeToastElement.click()));
| ^
48 | }
49 | }
50 |
at map (/app/front/tests/pages/common-page-model.ts:47:87)
at OperationalStudiesTimetablePage.closeToastNotification (/app/front/tests/pages/common-page-model.ts:47:42)
at OperationalStudiesTimetablePage.clickOnEditTrainSchedule (/app/front/tests/pages/op-timetable-page-model.ts:226:5)
at /app/front/tests/012-op-simulation-settings-tab.spec.ts:276:5
|
[webkit] › 006-stdcm.spec.ts:102:7 › Verify stdcm simulation page › Launch simulation with and without capacity for towed rolling stock:
tests/pages/stdcm-page-model.ts#L737
3) [webkit] › 006-stdcm.spec.ts:102:7 › Verify stdcm simulation page › Launch simulation with and without capacity for towed rolling stock
Error: expect(received).toEqual(expected) // deep equality
Expected: "Pas de capacité"
Received: "Simulation n°2"
at pages/stdcm-page-model.ts:737
735 | const actualSimulationName =
736 | await this.getSimulationNameLocator(simulationNumber).textContent();
> 737 | expect(actualSimulationName).toEqual(expectedSimulationName);
| ^
738 |
739 | // Determine expected length and duration
740 | const expectedLengthAndDuration = isResultTableVisible
at STDCMPage.verifySimulationDetails (/app/front/tests/pages/stdcm-page-model.ts:737:34)
at /app/front/tests/006-stdcm.spec.ts:132:5
|
Check scripts
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 final newline
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 dockerfiles
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 (core-build, core)
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
|
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
|
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 generated railjson sync
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 59.5s
|
Slow Test:
[firefox] › 006-stdcm.spec.ts#L1
[firefox] › 006-stdcm.spec.ts took 51.9s
|
Slow Test:
[firefox] › 009-rollingstock-editor.spec.ts#L1
[firefox] › 009-rollingstock-editor.spec.ts took 31.9s
|
Slow Test:
[chromium] › 013-stdcm-simulation-sheet.spec.ts#L1
[chromium] › 013-stdcm-simulation-sheet.spec.ts took 30.0s
|
🎭 Playwright Run Summary
3 flaky
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
[firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code
[webkit] › 006-stdcm.spec.ts:102:7 › Verify stdcm simulation page › Launch simulation with and without capacity for towed rolling stock
113 passed (17.5m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
e2e-container-logs
|
488 KB |
|
integration-container-logs
|
28.4 KB |
|
integration-videos
|
28.8 MB |
|