Skip to content

core: fix distance_range_map.to_range_map #10933

core: fix distance_range_map.to_range_map

core: fix distance_range_map.to_range_map #10933

Triggered via push September 13, 2024 08:01
Status Failure
Total duration 21m 4s
Artifacts 2

build.yml

on: push
Matrix: build
check_generated_railjson_sync
20s
check_generated_railjson_sync
check_railjson_generator
1m 44s
check_railjson_generator
check_commits
6s
check_commits
Check final newline
7s
Check final newline
check_integration_tests
1m 21s
check_integration_tests
check_osrd_schema
49s
check_osrd_schema
check_toml
5s
check_toml
check_infra_schema_sync
16s
check_infra_schema_sync
check_reuse_compliance
11s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 16 warnings, and 1 notice
[chromium] › 005-operational-studies.spec.ts:46: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:46: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:92:5
[chromium] › 005-operational-studies.spec.ts:46: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:46: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:92:5
[chromium] › 005-operational-studies.spec.ts:46: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:46: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:92:5
[chromium] › 005-operational-studies.spec.ts:46: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:46: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:92: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] › 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
3) [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 60000ms 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
[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
3) [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 60000ms 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
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/
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_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/
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/
Slow Test: [chromium] › 009-rollingstock-editor.spec.ts#L1
[chromium] › 009-rollingstock-editor.spec.ts took 27.7s
Slow Test: [firefox] › 008-train-schedule.spec.ts#L1
[firefox] › 008-train-schedule.spec.ts took 20.0s
Slow Test: [webkit] › 006-stdcm-page.spec.ts#L1
[webkit] › 006-stdcm-page.spec.ts took 16.9s
Slow Test: [webkit] › 004-scenario-management.spec.ts#L1
[webkit] › 004-scenario-management.spec.ts took 16.9s
🎭 Playwright Run Summary
7 failed [chromium] › 005-operational-studies.spec.ts:46: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 ──── [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:49:7 › Verifying that all elements in the route tab are loaded correctly › should correctly select a route for operational study [chromium] › 010-op-route-tab.spec.ts:81:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study [chromium] › 010-op-route-tab.spec.ts:125:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study 3 flaky [chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study [firefox] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario [webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study 76 passed (12.6m)

Artifacts

Produced during runtime
Name Size
integration-container-logs
262 KB
integration-videos
65.4 MB