Skip to content

core: stdcm: fix initialization of fixed time points in postproc #19739

core: stdcm: fix initialization of fixed time points in postproc

core: stdcm: fix initialization of fixed time points in postproc #19739

Triggered via pull request February 18, 2025 15:39
Status Success
Total duration 16m 39s
Artifacts 3

build.yml

on: pull_request
Matrix: Build
Check dockerfiles
14s
Check dockerfiles
Check scripts
5s
Check scripts
Check generated railjson sync
27s
Check generated railjson sync
Check railjson generator
29s
Check railjson generator
Check commits
11s
Check commits
Check final newline
11s
Check final newline
Check integration tests
1m 22s
Check integration tests
Check osrd schema
20s
Check osrd schema
Check toml
5s
Check toml
Check infra schema sync
15s
Check infra schema sync
Check reuse compliance
16s
Check reuse compliance
Check front rtk sync
1m 9s
Check front rtk sync
Check core
4m 16s
Check core
Check editoast tests
7m 0s
Check editoast tests
Check editoast lints
8m 36s
Check editoast lints
Check editoast openapi
48s
Check editoast openapi
Check gateway
3m 29s
Check gateway
Check osrdyne
4m 7s
Check osrdyne
Check front
3m 14s
Check front
Integration tests
1m 9s
Integration tests
End to end tests
8m 5s
End to end tests
Fit to window
Zoom out
Zoom in

Annotations

1 error, 4 warnings, and 1 notice
[chromium] › 006-stdcm.spec.ts:91:3 › Verify stdcm simulation page › Launch simulation with and without capacity for towed rolling stock: tests/pages/stdcm-page-model.ts#L667
1) [chromium] › 006-stdcm.spec.ts:91:3 › Verify stdcm simulation page › Launch simulation with and without capacity for towed rolling stock TimeoutError: locator.waitFor: Timeout 30000ms exceeded. Call log: - waiting for getByTestId('simulation-status') to be visible at pages/stdcm-page-model.ts:667 665 | await this.launchSimulationButton.click({ force: true }); 666 | // Wait for simulation message "Calculation completed" > 667 | await this.simulationStatus.waitFor({ timeout: STDCM_SIMULATION_TIMEOUT }); | ^ 668 | // Check map result container visibility only for Chromium browser 669 | if (this.page.context().browser()?.browserType().name() === 'chromium') { 670 | await expect(this.mapResultContainer).toBeVisible(); at STDCMPage.launchSimulation (/app/front/tests/pages/stdcm-page-model.ts:667:33) at /app/front/tests/006-stdcm.spec.ts:111:5
Slow Test: [chromium] › 008-train-schedule.spec.ts#L1
[chromium] › 008-train-schedule.spec.ts took 54.8s
Slow Test: [chromium] › 014-stdcm-linked-train.spec.ts#L1
[chromium] › 014-stdcm-linked-train.spec.ts took 35.6s
Slow Test: [chromium] › 013-stdcm-simulation-sheet.spec.ts#L1
[chromium] › 013-stdcm-simulation-sheet.spec.ts took 26.8s
Slow Test: [chromium] › 005-operational-studies.spec.ts#L1
[chromium] › 005-operational-studies.spec.ts took 21.8s
🎭 Playwright Run Summary
1 flaky [chromium] › 006-stdcm.spec.ts:91:3 › Verify stdcm simulation page › Launch simulation with and without capacity for towed rolling stock 81 passed (6.5m)

Artifacts

Produced during runtime
Name Size
e2e-container-logs
291 KB
e2e-traces-and-videos
9.18 MB
integration-container-logs
32.9 KB