front: add memoization to use scenario data and sub hooks #14820
Triggered via pull request
November 22, 2024 23:10
Synar
Status
Failure
Total duration
1h 49m 58s
Artifacts
3
build.yml
on: pull_request
Matrix: Build
Check dockerfiles
13s
Check scripts
4s
Check generated railjson sync
27s
Check railjson generator
1m 59s
Check commits
8s
Check final newline
37s
Check integration tests
1m 23s
Check osrd schema
43s
Check toml
9s
Check infra schema sync
22s
Check reuse compliance
10s
Check front rtk sync
1m 22s
Check core
4m 8s
Check editoast tests
6m 17s
Check editoast lints
8m 48s
Check editoast openapi
54s
Check gateway
3m 24s
Check osrdyne
3m 37s
Check front
2m 20s
Integration tests
1m 29s
End to end tests
1h 46m
Annotations
10 errors, 5 warnings, and 1 notice
|
[chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code:
tests/005-operational-studies.spec.ts#L1
1) [chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
Test timeout of 270000ms exceeded.
|
|
[chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code:
tests/pages/operational-studies-page-model.ts#L106
1) [chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
Error: locator.click: Test timeout of 270000ms exceeded.
Call log:
- waiting for getByTestId('return-simulation-result')
- locator resolved to <button type="button" class="btn btn-secondary btn-block…>…</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 is not visible
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element was detached from the DOM, retrying
at pages/operational-studies-page-model.ts:106
104 |
105 | async returnSimulationResult() {
> 106 | await this.returnSimulationResultButton.click();
| ^
107 | }
108 |
109 | async checkPathfindingDistance(distance: string | RegExp) {
at OperationalStudiesPage.returnSimulationResult (/app/front/tests/pages/operational-studies-page-model.ts:106:45)
at /app/front/tests/005-operational-studies.spec.ts:107:34
|
|
[chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code:
tests/005-operational-studies.spec.ts#L1
1) [chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 270000ms exceeded.
|
|
[chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code:
tests/pages/operational-studies-page-model.ts#L106
1) [chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 270000ms exceeded.
Call log:
- waiting for getByTestId('return-simulation-result')
- locator resolved to <button type="button" class="btn btn-secondary btn-block…>…</button>
- attempting click action
- waiting for element to be visible, enabled and stable
- element was detached from the DOM, retrying
at pages/operational-studies-page-model.ts:106
104 |
105 | async returnSimulationResult() {
> 106 | await this.returnSimulationResultButton.click();
| ^
107 | }
108 |
109 | async checkPathfindingDistance(distance: string | RegExp) {
at OperationalStudiesPage.returnSimulationResult (/app/front/tests/pages/operational-studies-page-model.ts:106:45)
at /app/front/tests/005-operational-studies.spec.ts:107:34
|
|
[chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code:
tests/pages/operational-studies-page-model.ts#L134
1) [chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 10000ms waiting for expect(locator).toHaveCount(expected)
Locator: locator('.scenario-timetable-trains').locator('.scenario-timetable-train')
Expected: 7
Received: 0
Call log:
- expect.toHaveCount with timeout 10000ms
- waiting for locator('.scenario-timetable-trains').locator('.scenario-timetable-train')
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
at pages/operational-studies-page-model.ts:134
132 |
133 | async checkNumberOfTrains(number: number) {
> 134 | await expect(this.trainTimetable).toHaveCount(number);
| ^
135 | }
136 | }
137 | export default OperationalStudiesPage;
at OperationalStudiesPage.checkNumberOfTrains (/app/front/tests/pages/operational-studies-page-model.ts:134:39)
at /app/front/tests/005-operational-studies.spec.ts:110:34
|
|
[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: 21
Received: 0
Call log:
- expect.toHaveCount with timeout 10000ms
- waiting for getByTestId('scenario-timetable-train')
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
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 /app/front/tests/008-train-schedule.spec.ts:53: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#L86
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Error: locator.innerText: Test ended.
Call log:
- waiting for getByTestId('invalid-trains-message')
at pages/op-timetable-page-model.ts:86
84 | async verifyInvalidTrainsMessageVisibility(selectedLanguage: string): Promise<void> {
85 | const translations = selectedLanguage === 'English' ? enTranslations : frTranslations;
> 86 | const invalidTrainsMessageText = await this.invalidTrainsMessage.innerText();
| ^
87 | expect(invalidTrainsMessageText).toEqual(translations.timetable.invalidTrains);
88 | }
89 |
at OperationalStudiesTimetablePage.verifyInvalidTrainsMessageVisibility (/app/front/tests/pages/op-timetable-page-model.ts:86:70)
at /app/front/tests/008-train-schedule.spec.ts:54:27
|
|
[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: 21
Received: 0
Call log:
- expect.toHaveCount with timeout 10000ms
- waiting for getByTestId('scenario-timetable-train')
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
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 /app/front/tests/008-train-schedule.spec.ts:53: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#L86
2) [chromium] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.innerText: Test ended.
Call log:
- waiting for getByTestId('invalid-trains-message')
at pages/op-timetable-page-model.ts:86
84 | async verifyInvalidTrainsMessageVisibility(selectedLanguage: string): Promise<void> {
85 | const translations = selectedLanguage === 'English' ? enTranslations : frTranslations;
> 86 | const invalidTrainsMessageText = await this.invalidTrainsMessage.innerText();
| ^
87 | expect(invalidTrainsMessageText).toEqual(translations.timetable.invalidTrains);
88 | }
89 |
at OperationalStudiesTimetablePage.verifyInvalidTrainsMessageVisibility (/app/front/tests/pages/op-timetable-page-model.ts:86:70)
at /app/front/tests/008-train-schedule.spec.ts:54:27
|
|
[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: 21
Received: 0
Call log:
- expect.toHaveCount with timeout 10000ms
- waiting for getByTestId('scenario-timetable-train')
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
- locator resolved to 0 elements
- unexpected value "0"
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 /app/front/tests/008-train-schedule.spec.ts:53:5
|
|
Slow Test:
[webkit] › 009-rollingstock-editor.spec.ts#L1
[webkit] › 009-rollingstock-editor.spec.ts took 56.3s
|
|
Slow Test:
[firefox] › 006-stdcm.spec.ts#L1
[firefox] › 006-stdcm.spec.ts took 49.5s
|
|
Slow Test:
[chromium] › 006-stdcm.spec.ts#L1
[chromium] › 006-stdcm.spec.ts took 48.9s
|
|
Slow Test:
[webkit] › 006-stdcm.spec.ts#L1
[webkit] › 006-stdcm.spec.ts took 48.1s
|
|
Slow Test:
[firefox] › 009-rollingstock-editor.spec.ts#L1
[firefox] › 009-rollingstock-editor.spec.ts took 32.0s
|
|
🎭 Playwright Run Summary
20 failed
[chromium] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
[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:131:7 › Simulation Settings Tab Verification › Activate electrical profiles
[chromium] › 012-op-simulation-settings-tab.spec.ts:186:7 › Simulation Settings Tab Verification › Activate composition code
[chromium] › 012-op-simulation-settings-tab.spec.ts:241:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
[chromium] › 012-op-simulation-settings-tab.spec.ts:305:7 › Simulation Settings Tab Verification › Add all the simulation settings
[firefox] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
[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:131:7 › Simulation Settings Tab Verification › Activate electrical profiles
[firefox] › 012-op-simulation-settings-tab.spec.ts:186:7 › Simulation Settings Tab Verification › Activate composition code
[firefox] › 012-op-simulation-settings-tab.spec.ts:241:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
[firefox] › 012-op-simulation-settings-tab.spec.ts:305:7 › Simulation Settings Tab Verification › Add all the simulation settings
[webkit] › 005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
[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
4 skipped
86 passed (1.7h)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
e2e-container-logs
|
439 KB |
|
|
integration-container-logs
|
24.3 KB |
|
|
integration-videos
|
103 MB |
|