editoast: use uom to type units #15626
Tristramgbuild.yml
on: pull_request
Matrix: Build
Check dockerfiles
8s
Check scripts
4s
Check generated railjson sync
22s
Check railjson generator
1m 46s
Check commits
7s
Check final newline
8s
Check integration tests
1m 22s
Check osrd schema
46s
Check toml
8s
Check infra schema sync
15s
Check reuse compliance
14s
Check front rtk sync
1m 10s
Check core
4m 5s
Check editoast tests
4m 3s
Check editoast lints
9m 2s
Check editoast openapi
5s
Check gateway
3m 25s
Check osrdyne
3m 42s
Check front
3m 12s
Integration tests
1m 7s
End to end tests
45m 40s
Annotations
15 errors, 31 warnings, and 1 notice
|
Check commits
Process completed with exit code 1.
|
|
Check editoast openapi
Process completed with exit code 1.
|
|
Integration tests
Process completed with exit code 1.
|
|
Check editoast tests
Process completed with exit code 101.
|
|
Check editoast lints
Process completed with exit code 101.
|
|
[chromium] › 006-stdcm.spec.ts:68:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet:
tests/006-stdcm.spec.ts#L1
1) [chromium] › 006-stdcm.spec.ts:68:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
Test timeout of 270000ms exceeded.
|
|
[chromium] › 006-stdcm.spec.ts:68:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet:
tests/006-stdcm.spec.ts#L1
1) [chromium] › 006-stdcm.spec.ts:68:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 270000ms exceeded.
|
|
[chromium] › 006-stdcm.spec.ts:68:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet:
tests/pages/stdcm-page-model.ts#L481
1) [chromium] › 006-stdcm.spec.ts:68:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 270000ms exceeded.
Call log:
- waiting for getByTestId('all-vias-button')
at pages/stdcm-page-model.ts:481
479 |
480 | async clickOnAllViaButton() {
> 481 | await this.allViasButton.click();
| ^
482 | }
483 |
484 | async clickOnRetainSimulation() {
at STDCMPage.clickOnAllViaButton (/app/front/tests/pages/stdcm-page-model.ts:481:30)
at /app/front/tests/006-stdcm.spec.ts:86:21
|
|
[chromium] › 006-stdcm.spec.ts:68:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet:
tests/006-stdcm.spec.ts#L1
1) [chromium] › 006-stdcm.spec.ts:68:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet
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#L156
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"
- locator resolved to 16 elements
- unexpected value "16"
- locator resolved to 16 elements
- unexpected value "16"
at pages/op-timetable-page-model.ts:156
154 | async verifyTrainCount(trainCount: number): Promise<void> {
155 | await this.page.waitForLoadState('networkidle');
> 156 | expect(this.timetableTrains).toHaveCount(trainCount);
| ^
157 | }
158 |
159 | // Filter trains validity and verify their count
at OperationalStudiesTimetablePage.verifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:156:34)
at OperationalStudiesTimetablePage.filterValidityAndVerifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:176: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#L204
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Error: page.waitForLoadState: Test ended.
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/pages/op-timetable-page-model.ts#L156
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"
at pages/op-timetable-page-model.ts:156
154 | async verifyTrainCount(trainCount: number): Promise<void> {
155 | await this.page.waitForLoadState('networkidle');
> 156 | expect(this.timetableTrains).toHaveCount(trainCount);
| ^
157 | }
158 |
159 | // Filter trains validity and verify their count
at OperationalStudiesTimetablePage.verifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:156:34)
at OperationalStudiesTimetablePage.filterValidityAndVerifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:176: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#L80
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:80
78 | // Wait for the simulation results to be in the DOM
79 | async waitForSimulationResults(): Promise<void> {
> 80 | await this.page.waitForSelector('.simulation-results', { state: 'attached' });
| ^
81 | }
82 |
83 | // Verify that the message "The timetable contains invalid trains" is visible
at OperationalStudiesTimetablePage.waitForSimulationResults (/app/front/tests/pages/op-timetable-page-model.ts:80:21)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:205: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#L156
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"
at pages/op-timetable-page-model.ts:156
154 | async verifyTrainCount(trainCount: number): Promise<void> {
155 | await this.page.waitForLoadState('networkidle');
> 156 | expect(this.timetableTrains).toHaveCount(trainCount);
| ^
157 | }
158 |
159 | // Filter trains validity and verify their count
at OperationalStudiesTimetablePage.verifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:156:34)
at OperationalStudiesTimetablePage.filterValidityAndVerifyTrainCount (/app/front/tests/pages/op-timetable-page-model.ts:176: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#L80
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: page.waitForSelector: Test ended.
Call log:
- waiting for locator('.simulation-results')
at pages/op-timetable-page-model.ts:80
78 | // Wait for the simulation results to be in the DOM
79 | async waitForSimulationResults(): Promise<void> {
> 80 | await this.page.waitForSelector('.simulation-results', { state: 'attached' });
| ^
81 | }
82 |
83 | // Verify that the message "The timetable contains invalid trains" is visible
at OperationalStudiesTimetablePage.waitForSimulationResults (/app/front/tests/pages/op-timetable-page-model.ts:80:21)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/front/tests/pages/op-timetable-page-model.ts:205:18)
at /app/front/tests/008-train-schedule.spec.ts:57: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 final newline
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 toml
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 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
|
|
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 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 (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
|
|
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 (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 editoast tests
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 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 55.7s
|
|
Slow Test:
[firefox] › 009-rollingstock-editor.spec.ts#L1
[firefox] › 009-rollingstock-editor.spec.ts took 32.0s
|
|
Slow Test:
[webkit] › 010-op-route-tab.spec.ts#L1
[webkit] › 010-op-route-tab.spec.ts took 28.4s
|
|
Slow Test:
[chromium] › 005-operational-studies.spec.ts#L1
[chromium] › 005-operational-studies.spec.ts took 22.9s
|
|
Slow Test:
[webkit] › 003-study-management.spec.ts#L1
[webkit] › 003-study-management.spec.ts took 20.0s
|
|
🎭 Playwright Run Summary
24 failed
[chromium] › 006-stdcm.spec.ts:68: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:130:7 › Simulation Settings Tab Verification › Activate electrical profiles
[chromium] › 012-op-simulation-settings-tab.spec.ts:184:7 › Simulation Settings Tab Verification › Activate composition code
[chromium] › 012-op-simulation-settings-tab.spec.ts:238:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
[chromium] › 012-op-simulation-settings-tab.spec.ts:301:7 › Simulation Settings Tab Verification › Add all the simulation settings
[firefox] › 006-stdcm.spec.ts:68: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:130:7 › Simulation Settings Tab Verification › Activate electrical profiles
[firefox] › 012-op-simulation-settings-tab.spec.ts:184:7 › Simulation Settings Tab Verification › Activate composition code
[firefox] › 012-op-simulation-settings-tab.spec.ts:238:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
[firefox] › 012-op-simulation-settings-tab.spec.ts:301:7 › Simulation Settings Tab Verification › Add all the simulation settings
[webkit] › 006-stdcm.spec.ts:68: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:130:7 › Simulation Settings Tab Verification › Activate electrical profiles
[webkit] › 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
[webkit] › 012-op-simulation-settings-tab.spec.ts:301:7 › Simulation Settings Tab Verification › Add all the simulation settings
86 passed (43.8m)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
e2e-container-logs
Expired
|
705 KB |
|
|
integration-container-logs
Expired
|
24 KB |
|
|
integration-videos
Expired
|
202 MB |
|