Skip to content

front: fix project image display in project page #17708

front: fix project image display in project page

front: fix project image display in project page #17708

Triggered via pull request January 16, 2025 13:09
Status Failure
Total duration 23m 37s
Artifacts 3

build.yml

on: pull_request
Matrix: Build
Check dockerfiles
13s
Check dockerfiles
Check scripts
5s
Check scripts
Check generated railjson sync
24s
Check generated railjson sync
Check railjson generator
1m 51s
Check railjson generator
Check commits
6s
Check commits
Check final newline
9s
Check final newline
Check integration tests
1m 21s
Check integration tests
Check osrd schema
40s
Check osrd schema
Check toml
5s
Check toml
Check infra schema sync
17s
Check infra schema sync
Check reuse compliance
9s
Check reuse compliance
Fit to window
Zoom out
Zoom in

Annotations

8 errors, 30 warnings, and 1 notice
Check commits
Process completed with exit code 1.
[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#L203
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: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
[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#L203
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: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] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code: tests/012-op-simulation-settings-tab.spec.ts#L1
2) [firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code Test timeout of 270000ms exceeded.
[firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code: tests/pages/common-page-model.ts#L47
2) [firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code Error: locator.click: Test timeout of 270000ms exceeded. Call log: - waiting for getByTestId('close-toast-button').first() - locator resolved to <button type="button" class="ml-2 close" data-testid="cl…>…</button> - attempting click action - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #2 - waiting 20ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #3 - waiting 100ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #4 - waiting 100ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #5 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #6 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #7 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #8 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #9 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #10 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #11 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not visible - retrying click action, attempt #12 - waiting 500ms - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying at pages/common-page-model.ts:47 45 | async closeToastNotification(): Promise<void> { 46 | const closeToastElements = await this.closeToastButton.all(); > 47 | await Promise.all(closeToastElements.map((closeToastElement) => closeToastElement.click())); | ^ 48 | } 49 | } 50 | at map (/app/front/tests/pages/common-page-model.ts:47:87) at OperationalStudiesTimetablePage.closeToastNotification (/app/front/tests/pages/common-page-model.ts:47:42) at OperationalStudiesTimetablePage.clickOnEditTrainSchedule (/app/front/tests/pages/op-timetable-page-model.ts:226:5) at /app/front/tests/012-op-simulation-settings-tab.spec.ts:276:5
[webkit] › 006-stdcm.spec.ts:102:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet: tests/pages/stdcm-page-model.ts#L696
3) [webkit] › 006-stdcm.spec.ts:102:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet Error: Timeout 90000ms exceeded while waiting on the predicate at pages/stdcm-page-model.ts:696 694 | await download.saveAs(downloadPath); 695 | logger.info(`The PDF was successfully downloaded to: ${downloadPath}`); > 696 | }).toPass({ | ^ 697 | timeout: EXPECT_TO_PASS_TIMEOUT, 698 | }); 699 | } at STDCMPage.downloadSimulation (/app/front/tests/pages/stdcm-page-model.ts:696:8) at /app/front/tests/006-stdcm.spec.ts:131:21
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 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
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 dockerfiles
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 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 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 (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 (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 editoast openapi
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
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
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] › 012-op-simulation-settings-tab.spec.ts#L1
[chromium] › 012-op-simulation-settings-tab.spec.ts took 1.6m
Slow Test: [chromium] › 006-stdcm.spec.ts#L1
[chromium] › 006-stdcm.spec.ts took 1.4m
Slow Test: [firefox] › 006-stdcm.spec.ts#L1
[firefox] › 006-stdcm.spec.ts took 1.2m
Slow Test: [firefox] › 009-rollingstock-editor.spec.ts#L1
[firefox] › 009-rollingstock-editor.spec.ts took 30.9s
Slow Test: [chromium] › 011-op-times-and-stops-tab.spec.ts#L1
[chromium] › 011-op-times-and-stops-tab.spec.ts took 27.8s
🎭 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 [firefox] › 012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code [webkit] › 006-stdcm.spec.ts:102:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet 110 passed (19.2m)

Artifacts

Produced during runtime
Name Size
e2e-container-logs
487 KB
integration-container-logs
29.7 KB
integration-videos
30 MB