editoast: fix projection endpoint #15631
build.yml
on: pull_request
Matrix: Build
Check dockerfiles
8s
Check scripts
3s
Check generated railjson sync
20s
Check railjson generator
1m 50s
Check commits
10s
Check final newline
26s
Check integration tests
1m 27s
Check osrd schema
38s
Check toml
5s
Check infra schema sync
14s
Check reuse compliance
9s
Check front rtk sync
1m 12s
Check core
4m 6s
Check editoast tests
5m 50s
Check editoast lints
9m 0s
Check editoast openapi
44s
Check gateway
3m 22s
Check osrdyne
3m 36s
Check front
3m 10s
Integration tests
1m 4s
End to end tests
16m 44s
Annotations
8 errors, 30 warnings, and 1 notice
Check commits
Process completed with exit code 1.
|
Check editoast tests
Process completed with exit code 101.
|
[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#L204
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:204
202 |
203 | for (let currentTrainIndex = 0; currentTrainIndex < trainCount; currentTrainIndex += 1) {
> 204 | await this.page.waitForLoadState('networkidle');
| ^
205 | await this.waitForSimulationResults();
206 | const trainButton = OperationalStudiesTimetablePage.getTrainButton(
207 | this.timetableTrains.nth(currentTrainIndex)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:204: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#L204
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:204
202 |
203 | for (let currentTrainIndex = 0; currentTrainIndex < trainCount; currentTrainIndex += 1) {
> 204 | await this.page.waitForLoadState('networkidle');
| ^
205 | await this.waitForSimulationResults();
206 | const trainButton = OperationalStudiesTimetablePage.getTrainButton(
207 | this.timetableTrains.nth(currentTrainIndex)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:204:23)
at /app/front/tests/008-train-schedule.spec.ts:57:5
|
[chromium] › 012-op-simulation-settings-tab.spec.ts:184:7 › Simulation Settings Tab Verification › Activate composition code:
tests/pages/op-timetable-page-model.ts#L232
2) [chromium] › 012-op-simulation-settings-tab.spec.ts:184:7 › Simulation Settings Tab Verification › Activate composition code
Error: expect(received).toEqual(expected) // deep equality
Expected: "11:52"
Received: "12:03"
at pages/op-timetable-page-model.ts:232
230 | await expect(this.trainArrivalTime).toBeVisible();
231 | const actualArrivalTime = await this.trainArrivalTime.textContent();
> 232 | expect(actualArrivalTime).toEqual(expectedArrivalTime);
| ^
233 | }
234 |
235 | async clickOnScenarioCollapseButton() {
at OperationalStudiesTimetablePage.getTrainArrivalTime (/app/front/tests/pages/op-timetable-page-model.ts:232:31)
at /app/front/tests/012-op-simulation-settings-tab.spec.ts:233:5
|
[webkit] › 012-op-simulation-settings-tab.spec.ts:238:7 › Simulation Settings Tab Verification › Activate linear and mareco margin:
tests/pages/operational-studies-page-model.ts#L98
3) [webkit] › 012-op-simulation-settings-tab.spec.ts:238:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
Error: Timed out 10000ms waiting for expect(locator).toHaveValue(expected)
Locator: locator('#trainSchedule-startTime')
Expected string: "2024-12-08T11:22:40"
Received string: "2024-12-08T15:46:17"
Call log:
- expect.toHaveValue with timeout 10000ms
- waiting for locator('#trainSchedule-startTime')
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
- locator resolved to <input step="1" type="datetime-local" value="2024-12-08…/>
- unexpected value "2024-12-08T15:46:17"
at pages/operational-studies-page-model.ts:98
96 | await this.startTimeField.waitFor({ state: 'visible' });
97 | await this.startTimeField.fill(startTime);
> 98 | await expect(this.startTimeField).toHaveValue(startTime);
| ^
99 | }
100 |
101 | async checkTrainHasBeenAdded() {
at OperationalStudiesPage.setTrainStartTime (/app/front/tests/pages/operational-studies-page-model.ts:98:39)
at /app/front/tests/012-op-simulation-settings-tab.spec.ts:115:7
|
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 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 (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 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 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 (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 final newline
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
|
Check osrd schema
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 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 (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 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] › 006-stdcm.spec.ts#L1
[chromium] › 006-stdcm.spec.ts took 52.5s
|
Slow Test:
[firefox] › 006-stdcm.spec.ts#L1
[firefox] › 006-stdcm.spec.ts took 50.5s
|
Slow Test:
[firefox] › 012-op-simulation-settings-tab.spec.ts#L1
[firefox] › 012-op-simulation-settings-tab.spec.ts took 38.5s
|
Slow Test:
[chromium] › 011-op-times-and-stops-tab.spec.ts#L1
[chromium] › 011-op-times-and-stops-tab.spec.ts took 33.4s
|
Slow Test:
[firefox] › 009-rollingstock-editor.spec.ts#L1
[firefox] › 009-rollingstock-editor.spec.ts took 30.2s
|
🎭 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
[chromium] › 012-op-simulation-settings-tab.spec.ts:184:7 › Simulation Settings Tab Verification › Activate composition code
[webkit] › 012-op-simulation-settings-tab.spec.ts:238:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
107 passed (15.1m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
e2e-container-logs
Expired
|
428 KB |
|
integration-container-logs
Expired
|
26.1 KB |
|
integration-videos
Expired
|
32.7 MB |
|