front: hide simulation sticky bar #13809
theocrsbbuild.yml
on: pull_request
Matrix: build
check_generated_railjson_sync
20s
check_railjson_generator
1m 50s
check_commits
7s
Check final newline
13s
check_integration_tests
1m 26s
check_osrd_schema
36s
check_toml
5s
check_infra_schema_sync
13s
check_reuse_compliance
8s
check_front_rtk_sync
1m 35s
check_core
4m 4s
check_editoast_tests
6m 31s
check_editoast_lints
9m 3s
check_editoast_openapi
1m 4s
check_gateway
3m 16s
check_osrdyne
3m 45s
check_front
2m 39s
integration_tests
12m 38s
Annotations
6 errors, 16 warnings, and 1 notice
|
[chromium] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario:
tests/utils/scenario.ts#L29
1) [chromium] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario
TypeError: Cannot read properties of undefined (reading 'id')
at utils/scenario.ts:29
27 | // Create a new scenario with a unique name
28 | const scenario = await postApiRequest(
> 29 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`,
| ^
30 | {
31 | ...scenarioData,
32 | name: `${scenarioData.name} ${uuidv4()}`,
at setupScenario (/app/tests/utils/scenario.ts:29:50)
at /app/tests/004-scenario-management.spec.ts:17:35
|
|
[firefox] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario:
tests/utils/scenario.ts#L29
2) [firefox] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario
TypeError: Cannot read properties of undefined (reading 'id')
at utils/scenario.ts:29
27 | // Create a new scenario with a unique name
28 | const scenario = await postApiRequest(
> 29 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`,
| ^
30 | {
31 | ...scenarioData,
32 | name: `${scenarioData.name} ${uuidv4()}`,
at setupScenario (/app/tests/utils/scenario.ts:29:50)
at /app/tests/004-scenario-management.spec.ts:17:35
|
|
[firefox] › 012-op-simulation-settings-tab.spec.ts:193:7 › Simulation Settings Tab Verification › Activate composition code:
tests/012-op-simulation-settings-tab.spec.ts#L1
3) [firefox] › 012-op-simulation-settings-tab.spec.ts:193:7 › Simulation Settings Tab Verification › Activate composition code
Test timeout of 90000ms exceeded.
|
|
[firefox] › 012-op-simulation-settings-tab.spec.ts:193:7 › Simulation Settings Tab Verification › Activate composition code:
tests/pages/op-timetable-page-model.ts#L215
3) [firefox] › 012-op-simulation-settings-tab.spec.ts:193:7 › Simulation Settings Tab Verification › Activate composition code
Error: locator.scrollIntoViewIfNeeded: Test timeout of 90000ms exceeded.
Call log:
- waiting for locator('.time-stops-datasheet')
at pages/op-timetable-page-model.ts:215
213 |
214 | async verifyTimeStopsDataSheetVisibility(timeout = 60 * 1000): Promise<void> {
> 215 | await this.timeStopsDataSheet.scrollIntoViewIfNeeded();
| ^
216 | // Wait for the Times and Stops simulation dataSheet to be fully loaded with a specified timeout (default: 60 seconds)
217 | await expect(this.timeStopsDataSheet).toBeVisible({ timeout });
218 | }
at OperationalStudiesTimetablePage.verifyTimeStopsDataSheetVisibility (/app/tests/pages/op-timetable-page-model.ts:215:35)
at /app/tests/012-op-simulation-settings-tab.spec.ts:243:27
|
|
[webkit] › 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#L1
4) [webkit] › 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
Test timeout of 120000ms exceeded.
|
|
[webkit] › 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/pages/op-timetable-page-model.ts#L204
4) [webkit] › 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
Error: page.waitForLoadState: Test timeout of 120000ms exceeded.
at pages/op-timetable-page-model.ts:204
202 |
203 | for (let currentTrainIndex = 0; currentTrainIndex < trainCount; currentTrainIndex += 1) {
> 204 | await this.page.waitForLoadState('networkidle');
| ^
205 | await this.waitForSimulationResults();
206 | const trainButton = OperationalStudiesTimetablePage.getTrainButton(
207 | this.timetableTrains.nth(currentTrainIndex)
at OperationalStudiesTimetablePage.verifyEachTrainSimulation (/app/tests/pages/op-timetable-page-model.ts:204:23)
at /app/tests/008-train-schedule.spec.ts:54:5
|
|
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 (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/
|
|
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 (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_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/
|
|
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_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_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:
[webkit] › 009-rollingstock-editor.spec.ts#L1
[webkit] › 009-rollingstock-editor.spec.ts took 57.2s
|
|
Slow Test:
[webkit] › 011-op-times-and-stops-tab.spec.ts#L1
[webkit] › 011-op-times-and-stops-tab.spec.ts took 50.0s
|
|
Slow Test:
[webkit] › 010-op-route-tab.spec.ts#L1
[webkit] › 010-op-route-tab.spec.ts took 38.3s
|
|
Slow Test:
[chromium] › 009-rollingstock-editor.spec.ts#L1
[chromium] › 009-rollingstock-editor.spec.ts took 30.9s
|
|
🎭 Playwright Run Summary
4 flaky
[chromium] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario
[firefox] › 004-scenario-management.spec.ts:21:7 › Test if scenario creation workflow is working properly › Create a new scenario
[firefox] › 012-op-simulation-settings-tab.spec.ts:193:7 › Simulation Settings Tab Verification › Activate composition code
[webkit] › 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
7 skipped
93 passed (9.7m)
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
integration-container-logs
Expired
|
326 KB |
|
|
integration-videos
Expired
|
21.9 MB |
|