Skip to content

front: add stdcm simulation sheet e2e test #16662

front: add stdcm simulation sheet e2e test

front: add stdcm simulation sheet e2e test #16662

Triggered via pull request December 24, 2024 13:32
Status Failure
Total duration 16m 49s
Artifacts 3

build.yml

on: pull_request
Matrix: Build
Check dockerfiles
8s
Check dockerfiles
Check scripts
6s
Check scripts
Check generated railjson sync
20s
Check generated railjson sync
Check railjson generator
1m 43s
Check railjson generator
Check commits
10s
Check commits
Check final newline
9s
Check final newline
Check integration tests
1m 30s
Check integration tests
Check osrd schema
48s
Check osrd schema
Check toml
11s
Check toml
Check infra schema sync
20s
Check infra schema sync
Check reuse compliance
8s
Check reuse compliance
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 28 warnings, and 1 notice
[chromium] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
1) [chromium] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ───────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/chromium 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[chromium] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
1) [chromium] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ───────────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/chromium 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[chromium] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
1) [chromium] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ───────────────────── Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/chromium 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[firefox] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
2) [firefox] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ────────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/firefox 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[firefox] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
2) [firefox] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ────────────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/firefox 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[firefox] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
2) [firefox] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ────────────────────── Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/firefox 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[webkit] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
3) [webkit] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ─────────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/webkit 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[webkit] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
3) [webkit] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ─────────────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/webkit 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[webkit] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content: tests/013-stdcm-simulation-sheet.spec.ts#L32
3) [webkit] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ─────────────────────── Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: No PDF files found in directory: ./tests/stdcm-results/webkit 30 | 31 | if (!pdfFilePath) { > 32 | throw new Error(`No PDF files found in directory: ${downloadDir}`); | ^ 33 | } 34 | 35 | // Read and parse the PDF at /app/front/tests/013-stdcm-simulation-sheet.spec.ts:32:11
[webkit] › 006-stdcm.spec.ts:70:7 › Verify train schedule elements and filters › Launch STDCM simulation with all stops: tests/pages/stdcm-page-model.ts#L616
4) [webkit] › 006-stdcm.spec.ts:70:7 › Verify train schedule elements and filters › Launch STDCM simulation with all stops Error: Timed out 10000ms waiting for expect(locator).toBeEnabled() Locator: getByTestId('launch-simulation-button') Expected: enabled Received: disabled Call log: - expect.toBeEnabled with timeout 10000ms - waiting for getByTestId('launch-simulation-button') - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" - locator resolved to <button disabled data-testid="launch-simulation-button" …>Obtenir la simulation</button> - unexpected value "disabled" Call Log: - Timeout 90000ms exceeded while waiting on the predicate at pages/stdcm-page-model.ts:616 614 | await expect(this.mapResultContainer).toBeVisible(); 615 | } > 616 | }).toPass({ | ^ 617 | timeout: EXPECT_TO_PASS_TIMEOUT, 618 | }); 619 | } at STDCMPage.launchSimulation (/app/front/tests/pages/stdcm-page-model.ts:616:8) at /app/front/tests/006-stdcm.spec.ts:92: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 dockerfiles
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
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
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 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
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
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 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
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] › 005-operational-studies.spec.ts#L1
[chromium] › 005-operational-studies.spec.ts took 18.0s
Slow Test: [chromium] › 007-op-rollingstock-tab.spec.ts#L1
[chromium] › 007-op-rollingstock-tab.spec.ts took 16.3s
🎭 Playwright Run Summary
3 failed [chromium] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ────────────────────── [firefox] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ─────────────────────── [webkit] › 013-stdcm-simulation-sheet.spec.ts:21:5 › Verify PDF content ──────────────────────── 2 flaky [webkit] › 006-stdcm.spec.ts:70:7 › Verify train schedule elements and filters › Launch STDCM simulation with all stops [webkit] › 006-stdcm.spec.ts:97:7 › Verify train schedule elements and filters › Verify STDCM stops and simulation sheet 111 passed (12.8m)

Artifacts

Produced during runtime
Name Size
e2e-container-logs
449 KB
integration-container-logs
29.6 KB
integration-videos
21.2 MB