Skip to content

front: stdcm: persist user-entered date and time in the interface #11272

front: stdcm: persist user-entered date and time in the interface

front: stdcm: persist user-entered date and time in the interface #11272

Triggered via pull request September 23, 2024 04:11
Status Failure
Total duration 23m 41s
Artifacts 2

build.yml

on: pull_request
Matrix: build
check_generated_railjson_sync
20s
check_generated_railjson_sync
check_railjson_generator
1m 48s
check_railjson_generator
check_commits
8s
check_commits
Check final newline
7s
Check final newline
check_integration_tests
1m 29s
check_integration_tests
check_osrd_schema
36s
check_osrd_schema
check_toml
7s
check_toml
check_infra_schema_sync
24s
check_infra_schema_sync
check_reuse_compliance
9s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

11 errors, 12 warnings, and 1 notice
check_commits
Process completed with exit code 1.
[chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code: tests/pages/scenario-page-model.ts#L267
1) [chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('result-pathfinding-done') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('result-pathfinding-done') at pages/scenario-page-model.ts:267 265 | ).toBeVisible(); 266 | await this.getSearchByTrigramsubmit.click(); > 267 | await expect(this.getResultPathfindingDone).toBeVisible(); | ^ 268 | } 269 | 270 | async clickBtnByName(name: string) { at ScenarioPage.getPathfindingByTriGramSearch (/app/tests/pages/scenario-page-model.ts:267:49) at /app/tests/005-operational-studies.spec.ts:71:5
[chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code: tests/pages/scenario-page-model.ts#L267
1) [chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('result-pathfinding-done') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('result-pathfinding-done') at pages/scenario-page-model.ts:267 265 | ).toBeVisible(); 266 | await this.getSearchByTrigramsubmit.click(); > 267 | await expect(this.getResultPathfindingDone).toBeVisible(); | ^ 268 | } 269 | 270 | async clickBtnByName(name: string) { at ScenarioPage.getPathfindingByTriGramSearch (/app/tests/pages/scenario-page-model.ts:267:49) at /app/tests/005-operational-studies.spec.ts:71:5
[chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code: tests/pages/scenario-page-model.ts#L267
1) [chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('result-pathfinding-done') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('result-pathfinding-done') at pages/scenario-page-model.ts:267 265 | ).toBeVisible(); 266 | await this.getSearchByTrigramsubmit.click(); > 267 | await expect(this.getResultPathfindingDone).toBeVisible(); | ^ 268 | } 269 | 270 | async clickBtnByName(name: string) { at ScenarioPage.getPathfindingByTriGramSearch (/app/tests/pages/scenario-page-model.ts:267:49) at /app/tests/005-operational-studies.spec.ts:71:5
[chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code: tests/pages/scenario-page-model.ts#L267
1) [chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('result-pathfinding-done') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('result-pathfinding-done') at pages/scenario-page-model.ts:267 265 | ).toBeVisible(); 266 | await this.getSearchByTrigramsubmit.click(); > 267 | await expect(this.getResultPathfindingDone).toBeVisible(); | ^ 268 | } 269 | 270 | async clickBtnByName(name: string) { at ScenarioPage.getPathfindingByTriGramSearch (/app/tests/pages/scenario-page-model.ts:267:49) at /app/tests/005-operational-studies.spec.ts:71:5
[chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm: tests/pages/simulation-conf-page.ts#L57
2) [chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm ─── Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('result-pathfinding-done') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('result-pathfinding-done') at pages/simulation-conf-page.ts:57 55 | ).toBeVisible(); 56 | await this.searchByTrigramSubmitButton.click(); > 57 | await expect(this.pathfindingDoneLabel).toBeVisible(); | ^ 58 | } 59 | } 60 | export default SimulationConfPage; at StdcmPage.selectPathByTrigram (/app/tests/pages/simulation-conf-page.ts:57:45) at /app/tests/006-stdcm-page.spec.ts:47:5
[chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm: tests/pages/simulation-conf-page.ts#L57
2) [chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm ─── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('result-pathfinding-done') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('result-pathfinding-done') at pages/simulation-conf-page.ts:57 55 | ).toBeVisible(); 56 | await this.searchByTrigramSubmitButton.click(); > 57 | await expect(this.pathfindingDoneLabel).toBeVisible(); | ^ 58 | } 59 | } 60 | export default SimulationConfPage; at StdcmPage.selectPathByTrigram (/app/tests/pages/simulation-conf-page.ts:57:45) at /app/tests/006-stdcm-page.spec.ts:47:5
[chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm: tests/pages/simulation-conf-page.ts#L57
2) [chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm ─── Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('result-pathfinding-done') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('result-pathfinding-done') at pages/simulation-conf-page.ts:57 55 | ).toBeVisible(); 56 | await this.searchByTrigramSubmitButton.click(); > 57 | await expect(this.pathfindingDoneLabel).toBeVisible(); | ^ 58 | } 59 | } 60 | export default SimulationConfPage; at StdcmPage.selectPathByTrigram (/app/tests/pages/simulation-conf-page.ts:57:45) at /app/tests/006-stdcm-page.spec.ts:47:5
[chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm: tests/pages/simulation-conf-page.ts#L57
2) [chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm ─── Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: getByTestId('result-pathfinding-done') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for getByTestId('result-pathfinding-done') at pages/simulation-conf-page.ts:57 55 | ).toBeVisible(); 56 | await this.searchByTrigramSubmitButton.click(); > 57 | await expect(this.pathfindingDoneLabel).toBeVisible(); | ^ 58 | } 59 | } 60 | export default SimulationConfPage; at StdcmPage.selectPathByTrigram (/app/tests/pages/simulation-conf-page.ts:57:45) at /app/tests/006-stdcm-page.spec.ts:47:5
[chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario: tests/utils/scenario.ts#L27
3) [chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario TypeError: Cannot read properties of undefined (reading 'id') at utils/scenario.ts:27 25 | // Create a new scenario with a unique name 26 | const scenario = await postApiRequest( > 27 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`, | ^ 28 | { 29 | ...scenarioData, 30 | name: `${scenarioData.name} ${uuidv4()}`, at setupScenario (/app/tests/utils/scenario.ts:27:50) at /app/tests/004-scenario-management.spec.ts:17:35
[chromium] › 008-train-schedule.spec.ts:39:7 › Verifying that all elements in the train schedule are loaded correctly › should accurately load the trains with their corresponding simulation results: tests/008-train-schedule.spec.ts#L19
4) [chromium] › 008-train-schedule.spec.ts:39:7 › Verifying that all elements in the train schedule are loaded correctly › should accurately load the trains with their corresponding simulation results "beforeAll" hook timeout of 90000ms exceeded. 17 | const trainSchedulesJson = readJsonFile('./tests/assets/trainSchedule/train_schedules.json'); 18 | > 19 | test.beforeAll(async () => { | ^ 20 | ({ project, study, scenario } = await setupScenario()); 21 | 22 | // Post train schedule import and simulation at /app/tests/008-train-schedule.spec.ts:19:6
🎭 Playwright Run Summary
2 failed [chromium] › 005-operational-studies.spec.ts:25:7 › Testing if all mandatory elements simulation configuration are loaded in operationnal studies app › Testing pathfinding with rollingstock and composition code [chromium] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm ──── 6 flaky [chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario [chromium] › 008-train-schedule.spec.ts:39:7 › Verifying that all elements in the train schedule are loaded correctly › should accurately load the trains with their corresponding simulation results [chromium] › 008-train-schedule.spec.ts:57:7 › Verifying that all elements in the train schedule are loaded correctly › should accurately filter the imported trains [chromium] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study [firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario [firefox] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study 78 passed (8.8m)
build (core-build, core)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (editoast, editoast-test)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (osrdyne, osrdyne-test)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_railjson_generator
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (gateway-test, gateway-standalone, gateway-front)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (front-build, front-tests, front-devel, front-nginx)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_gateway
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_front
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_osrdyne
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_core
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_editoast_tests
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration_tests
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
integration-container-logs
257 KB
integration-videos
45.2 MB