front: bump @typescript-eslint/eslint-plugin from 8.20.0 to 8.21.0 in /front #17959
dependabot[bot]build.yml
on: pull_request
Matrix: Build
Check dockerfiles
9s
Check scripts
4s
Check generated railjson sync
22s
Check railjson generator
1m 54s
Check commits
9s
Check final newline
12s
Check integration tests
1m 20s
Check osrd schema
39s
Check toml
4s
Check infra schema sync
16s
Check reuse compliance
9s
Check front rtk sync
1m 13s
Check core
4m 21s
Check editoast tests
6m 57s
Check editoast lints
8m 14s
Check editoast openapi
43s
Check gateway
3m 27s
Check osrdyne
3m 40s
Check front
3m 21s
Integration tests
1m 1s
End to end tests
27m 47s
Annotations
10 errors, 31 warnings, and 1 notice
|
[webkit] › 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) [webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Test timeout of 270000ms exceeded.
|
|
[webkit] › 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) [webkit] › 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
|
|
[webkit] › 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) [webkit] › 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.
|
|
[webkit] › 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#L208
1) [webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 270000ms exceeded.
Call log:
- waiting for getByTestId('scenario-timetable-train').nth(9).getByTestId('scenario-timetable-train-button')
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #3
- waiting 100ms
- 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 #4
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element was detached from the DOM, retrying
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- <div class="scenario-timetable-toolbar">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #3
- waiting 100ms
- 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
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- <div class="scenario-timetable-toolbar">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
-
|
|
[webkit] › 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) [webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 270000ms exceeded.
|
|
[webkit] › 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) [webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
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] › 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
2) [firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Test timeout of 270000ms exceeded.
|
|
[firefox] › 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#L208
2) [firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Error: locator.click: Test timeout of 270000ms exceeded.
Call log:
- waiting for getByTestId('scenario-timetable-train').nth(10).getByTestId('scenario-timetable-train-button')
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- performing click action
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #3
- waiting 100ms
- 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
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- <div class="scenario-timetable-toolbar">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- performing click action
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #3
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-toolbar">…</div> intercepts pointer events
- retrying click action, attempt #4
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element was detached from the DOM, retrying
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- <div class="scenario-timetable-toolbar">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- performing click action
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
|
|
[firefox] › 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
2) [firefox] › 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.
|
|
[firefox] › 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#L208
2) [firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 270000ms exceeded.
Call log:
- waiting for getByTestId('scenario-timetable-train').nth(8).getByTestId('scenario-timetable-train-button')
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- performing click action
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #3
- waiting 100ms
- 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
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- <div class="scenario-timetable-toolbar">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- performing click action
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #2
- waiting 20ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, attempt #3
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- <div class="scenario-timetable-toolbar">…</div> intercepts pointer events
- retrying click action, attempt #4
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element was detached from the DOM, retrying
- locator resolved to <div tabindex="0" role="button" class="w-full clickab…>…</div>
- 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
- <div class="scenario-timetable-toolbar">…</div> intercepts pointer events
- retrying click action, attempt #1
- waiting for element to be visible, enabled and stable
- element is visible, enabled and stable
- scrolling into view if needed
- done scrolling
- performing click action
- <div class="scenario-timetable-trains">…</div> intercepts pointer events
- retrying click action, a
|
|
Check dockerfiles
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636
|
|
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 toml
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
|
|
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 (core-build, core)
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
|
|
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 (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
|
|
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] › 012-op-simulation-settings-tab.spec.ts#L1
[webkit] › 012-op-simulation-settings-tab.spec.ts took 1.8m
|
|
Slow Test:
[webkit] › 009-rollingstock-editor.spec.ts#L1
[webkit] › 009-rollingstock-editor.spec.ts took 58.0s
|
|
Slow Test:
[firefox] › 012-op-simulation-settings-tab.spec.ts#L1
[firefox] › 012-op-simulation-settings-tab.spec.ts took 55.7s
|
|
Slow Test:
[firefox] › 006-stdcm.spec.ts#L1
[firefox] › 006-stdcm.spec.ts took 52.1s
|
|
Slow Test:
[webkit] › 011-op-times-and-stops-tab.spec.ts#L1
[webkit] › 011-op-times-and-stops-tab.spec.ts took 34.0s
|
|
🎭 Playwright Run Summary
1 failed
[webkit] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
3 flaky
[firefox] › 008-train-schedule.spec.ts:49:7 › Verify train schedule elements and filters › Loading trains and verifying simulation result
[webkit] › 006-stdcm.spec.ts:102:7 › Verify stdcm simulation page › Launch simulation with and without capacity for towed rolling stock
[webkit] › 013-stdcm-simulation-sheet.spec.ts:60:7 › Verify stdcm simulation page › Verify STDCM stops and simulation sheet
112 passed (26.0m)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
e2e-container-logs
|
516 KB |
|
|
integration-container-logs
|
27.9 KB |
|
|
integration-videos
|
283 MB |
|