editoast: use uom to type units #16686
Tristramgbuild.yml
on: pull_request
Matrix: Build
Check dockerfiles
8s
Check scripts
5s
Check generated railjson sync
18s
Check railjson generator
1m 49s
Check commits
8s
Check final newline
8s
Check integration tests
1m 23s
Check osrd schema
45s
Check toml
5s
Check infra schema sync
20s
Check reuse compliance
9s
Check front rtk sync
1m 15s
Check core
4m 3s
Check editoast tests
6m 57s
Check editoast lints
9m 40s
Check editoast openapi
45s
Check gateway
3m 19s
Check osrdyne
3m 40s
Check front
3m 13s
Integration tests
1m 16s
End to end tests
36m 18s
Annotations
10 errors, 30 warnings, and 1 notice
|
[chromium] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet:
tests/pages/stdcm-page-model.ts#L701
1) [chromium] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
Error: Timed out 10000ms waiting for expect(locator).toBeVisible()
Locator: locator('#map-result').locator('img[alt="origin"]')
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 10000ms
- waiting for locator('#map-result').locator('img[alt="origin"]')
at pages/stdcm-page-model.ts:701
699 |
700 | async mapMarkerResultVisibility() {
> 701 | await expect(this.originResultMarker).toBeVisible();
| ^
702 | await expect(this.destinationResultMarker).toBeVisible();
703 | await expect(this.viaResultMarker).toBeVisible();
704 | }
at STDCMPage.mapMarkerResultVisibility (/app/front/tests/pages/stdcm-page-model.ts:701:43)
at /app/front/tests/006-stdcm.spec.ts:120:23
|
|
[chromium] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet:
tests/pages/stdcm-page-model.ts#L701
1) [chromium] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 10000ms waiting for expect(locator).toBeVisible()
Locator: locator('#map-result').locator('img[alt="origin"]')
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 10000ms
- waiting for locator('#map-result').locator('img[alt="origin"]')
at pages/stdcm-page-model.ts:701
699 |
700 | async mapMarkerResultVisibility() {
> 701 | await expect(this.originResultMarker).toBeVisible();
| ^
702 | await expect(this.destinationResultMarker).toBeVisible();
703 | await expect(this.viaResultMarker).toBeVisible();
704 | }
at STDCMPage.mapMarkerResultVisibility (/app/front/tests/pages/stdcm-page-model.ts:701:43)
at /app/front/tests/006-stdcm.spec.ts:120:23
|
|
[chromium] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet:
tests/pages/stdcm-page-model.ts#L701
1) [chromium] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 10000ms waiting for expect(locator).toBeVisible()
Locator: locator('#map-result').locator('img[alt="origin"]')
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 10000ms
- waiting for locator('#map-result').locator('img[alt="origin"]')
at pages/stdcm-page-model.ts:701
699 |
700 | async mapMarkerResultVisibility() {
> 701 | await expect(this.originResultMarker).toBeVisible();
| ^
702 | await expect(this.destinationResultMarker).toBeVisible();
703 | await expect(this.viaResultMarker).toBeVisible();
704 | }
at STDCMPage.mapMarkerResultVisibility (/app/front/tests/pages/stdcm-page-model.ts:701:43)
at /app/front/tests/006-stdcm.spec.ts:120:23
|
|
[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#L155
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Error: Timed out 10000ms waiting for expect(locator).toHaveCount(expected)
Locator: getByTestId('scenario-timetable-train')
Expected: 17
Received: 16
Call log:
- expect.toHaveCount with timeout 10000ms
- waiting for getByTestId('scenario-timetable-train')
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
at pages/op-timetable-page-model.ts:155
153 | async verifyTrainCount(trainCount: number): Promise<void> {
154 | await this.page.waitForLoadState('networkidle');
> 155 | expect(this.timetableTrains).toHaveCount(trainCount);
| ^
156 | }
157 |
158 | // Filter trains validity and verify their count
at OperationalStudiesTimetablePage.verifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:155:34)
at OperationalStudiesTimetablePage.filterValidityAndVerifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:175:5)
at /app/front/tests/008-train-schedule.spec.ts:56:5
|
|
[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#L79
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Error: page.waitForSelector: Test ended.
Call log:
- waiting for locator('.simulation-results')
at pages/op-timetable-page-model.ts:79
77 | // Wait for the simulation results to be in the DOM
78 | async waitForSimulationResults(): Promise<void> {
> 79 | await this.page.waitForSelector('.simulation-results', { state: 'attached' });
| ^
80 | }
81 |
82 | // Verify that the message "The timetable contains invalid trains" is visible
at OperationalStudiesTimetablePage.waitForSimulationResults (/app/front/tests/pages/op-timetable-page-model.ts:79:21)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:204:18)
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/pages/op-timetable-page-model.ts#L155
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 10000ms waiting for expect(locator).toHaveCount(expected)
Locator: getByTestId('scenario-timetable-train')
Expected: 17
Received: 16
Call log:
- expect.toHaveCount with timeout 10000ms
- waiting for getByTestId('scenario-timetable-train')
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
at pages/op-timetable-page-model.ts:155
153 | async verifyTrainCount(trainCount: number): Promise<void> {
154 | await this.page.waitForLoadState('networkidle');
> 155 | expect(this.timetableTrains).toHaveCount(trainCount);
| ^
156 | }
157 |
158 | // Filter trains validity and verify their count
at OperationalStudiesTimetablePage.verifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:155:34)
at OperationalStudiesTimetablePage.filterValidityAndVerifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:175:5)
at /app/front/tests/008-train-schedule.spec.ts:56:5
|
|
[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#L79
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: page.waitForSelector: Test ended.
Call log:
- waiting for locator('.simulation-results')
- locator resolved to visible <div class="simulation-results">…</div>
at pages/op-timetable-page-model.ts:79
77 | // Wait for the simulation results to be in the DOM
78 | async waitForSimulationResults(): Promise<void> {
> 79 | await this.page.waitForSelector('.simulation-results', { state: 'attached' });
| ^
80 | }
81 |
82 | // Verify that the message "The timetable contains invalid trains" is visible
at OperationalStudiesTimetablePage.waitForSimulationResults (/app/front/tests/pages/op-timetable-page-model.ts:79:21)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:204:18)
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/pages/op-timetable-page-model.ts#L155
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 10000ms waiting for expect(locator).toHaveCount(expected)
Locator: getByTestId('scenario-timetable-train')
Expected: 17
Received: 16
Call log:
- expect.toHaveCount with timeout 10000ms
- waiting for getByTestId('scenario-timetable-train')
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
at pages/op-timetable-page-model.ts:155
153 | async verifyTrainCount(trainCount: number): Promise<void> {
154 | await this.page.waitForLoadState('networkidle');
> 155 | expect(this.timetableTrains).toHaveCount(trainCount);
| ^
156 | }
157 |
158 | // Filter trains validity and verify their count
at OperationalStudiesTimetablePage.verifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:155:34)
at OperationalStudiesTimetablePage.filterValidityAndVerifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:175:5)
at /app/front/tests/008-train-schedule.spec.ts:56:5
|
|
[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#L68
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.waitFor: Test ended.
Call log:
- waiting for locator('.manchette-space-time-chart-wrapper') to be visible
at pages/op-timetable-page-model.ts:68
66 | // Function to wait for an element to be visible and then assert its visibility
67 | static async waitForElementVisibility(locator: Locator): Promise<void> {
> 68 | await locator.waitFor({ state: 'visible', timeout: 30 * 1000 });
| ^
69 | await expect(locator).toBeVisible();
70 | }
71 |
at Function.waitForElementVisibility (/app/front/tests/pages/op-timetable-page-model.ts:68:19)
at map (/app/front/tests/pages/op-timetable-page-model.ts:110:41)
at OperationalStudiesTimetablePage.verifySimulationResultsVisibility (/app/front/tests/pages/op-timetable-page-model.ts:109:33)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:209:7)
at /app/front/tests/008-train-schedule.spec.ts:57:5
|
|
[chromium] › 008-train-schedule.spec.ts:61:7 › Verify train schedule elements and filters › Filtering imported trains:
tests/pages/op-timetable-page-model.ts#L155
3) [chromium] › 008-train-schedule.spec.ts:61:7 › Verify train schedule elements and filters › Filtering imported trains
Error: expect(locator).toHaveCount(expected)
Locator: getByTestId('scenario-timetable-train')
Expected: 4
Received: 21
Call log:
- expect.toHaveCount with timeout 10000ms
- waiting for getByTestId('scenario-timetable-train')
- locator resolved to 5 elements
- unexpected value "5"
- locator resolved to 5 elements
- unexpected value "5"
- locator resolved to 21 elements
- unexpected value "21"
- locator resolved to 21 elements
- unexpected value "21"
- locator resolved to 21 elements
- unexpected value "21"
- locator resolved to 21 elements
- unexpected value "21"
at pages/op-timetable-page-model.ts:155
153 | async verifyTrainCount(trainCount: number): Promise<void> {
154 | await this.page.waitForLoadState('networkidle');
> 155 | expect(this.timetableTrains).toHaveCount(trainCount);
| ^
156 | }
157 |
158 | // Filter trains validity and verify their count
at OperationalStudiesTimetablePage.verifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:155:34)
at OperationalStudiesTimetablePage.filterHonoredAndVerifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:195:5)
at /app/front/tests/008-train-schedule.spec.ts:88: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 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 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 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 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 (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 (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 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:
[webkit] › 009-rollingstock-editor.spec.ts#L1
[webkit] › 009-rollingstock-editor.spec.ts took 56.0s
|
|
Slow Test:
[webkit] › 010-op-route-tab.spec.ts#L1
[webkit] › 010-op-route-tab.spec.ts took 24.9s
|
|
Slow Test:
[chromium] › 005-operational-studies.spec.ts#L1
[chromium] › 005-operational-studies.spec.ts took 19.3s
|
|
Slow Test:
[chromium] › 007-op-rollingstock-tab.spec.ts#L1
[chromium] › 007-op-rollingstock-tab.spec.ts took 16.2s
|
|
🎭 Playwright Run Summary
24 failed
[chromium] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
[chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
[chromium] › 008-train-schedule.spec.ts:61:7 › Verify train schedule elements and filters › Filtering imported trains
[chromium] › 011-op-times-and-stops-tab.spec.ts:115:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables
[chromium] › 012-op-simulation-settings-tab.spec.ts:134:7 › Simulation Settings Tab Verification › Activate electrical profiles
[chromium] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code
[chromium] › 012-op-simulation-settings-tab.spec.ts:295:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
[chromium] › 012-op-simulation-settings-tab.spec.ts:384:7 › Simulation Settings Tab Verification › Add all the simulation settings
[firefox] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
[firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
[firefox] › 008-train-schedule.spec.ts:61:7 › Verify train schedule elements and filters › Filtering imported trains
[firefox] › 011-op-times-and-stops-tab.spec.ts:115:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables
[firefox] › 012-op-simulation-settings-tab.spec.ts:134:7 › Simulation Settings Tab Verification › Activate electrical profiles
[firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code
[firefox] › 012-op-simulation-settings-tab.spec.ts:295:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
[firefox] › 012-op-simulation-settings-tab.spec.ts:384:7 › Simulation Settings Tab Verification › Add all the simulation settings
[webkit] › 006-stdcm.spec.ts:97: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
[webkit] › 008-train-schedule.spec.ts:61:7 › Verify train schedule elements and filters › Filtering imported trains
[webkit] › 011-op-times-and-stops-tab.spec.ts:115:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables
[webkit] › 012-op-simulation-settings-tab.spec.ts:134:7 › Simulation Settings Tab Verification › Activate electrical profiles
[webkit] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code
[webkit] › 012-op-simulation-settings-tab.spec.ts:295:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
[webkit] › 012-op-simulation-settings-tab.spec.ts:384:7 › Simulation Settings Tab Verification › Add all the simulation settings
89 passed (34.6m)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
e2e-container-logs
|
802 KB |
|
|
integration-container-logs
|
29.7 KB |
|
|
integration-videos
|
181 MB |
|