front: replace some type assertions with non-null assertions #10798
emersionbuild.yml
on: pull_request
Matrix: build
check_generated_railjson_sync
26s
check_railjson_generator
1m 51s
check_commits
6s
Check final newline
12s
check_integration_tests
1m 22s
check_osrd_schema
42s
check_toml
9s
check_infra_schema_sync
18s
check_reuse_compliance
8s
check_front_rtk_sync
1m 42s
check_core
4m 2s
check_editoast_tests
4m 17s
check_editoast_lints
4m 58s
check_editoast_openapi
1m 15s
check_gateway
2m 14s
check_osrdyne
2m 37s
check_front
2m 43s
integration_tests
1h 39m
Annotations
10 errors, 16 warnings, and 1 notice
|
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/004-scenario-management.spec.ts#L1
1) [chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Test timeout of 60000ms exceeded.
|
|
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/004-scenario-management.spec.ts#L65
1) [chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Error: locator.textContent: Test timeout of 60000ms exceeded.
Call log:
- waiting for locator('.scenario-details-name .scenario-name')
63 | await createButton.click();
64 | await homePage.page.waitForURL('**/scenarios/*');
> 65 | expect(await scenarioPage.getScenarioName.textContent()).toContain(scenarioName);
| ^
66 | expect(await scenarioPage.getScenarioDescription.textContent()).toContain(
67 | scenarioData.description
68 | );
at /app/tests/004-scenario-management.spec.ts:65:47
|
|
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/004-scenario-management.spec.ts#L1
1) [chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 60000ms exceeded.
|
|
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/004-scenario-management.spec.ts#L65
1) [chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.textContent: Test timeout of 60000ms exceeded.
Call log:
- waiting for locator('.scenario-details-name .scenario-name')
63 | await createButton.click();
64 | await homePage.page.waitForURL('**/scenarios/*');
> 65 | expect(await scenarioPage.getScenarioName.textContent()).toContain(scenarioName);
| ^
66 | expect(await scenarioPage.getScenarioDescription.textContent()).toContain(
67 | scenarioData.description
68 | );
at /app/tests/004-scenario-management.spec.ts:65:47
|
|
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/004-scenario-management.spec.ts#L1
1) [chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 60000ms exceeded.
|
|
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/004-scenario-management.spec.ts#L65
1) [chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.textContent: Test timeout of 60000ms exceeded.
Call log:
- waiting for locator('.scenario-details-name .scenario-name')
63 | await createButton.click();
64 | await homePage.page.waitForURL('**/scenarios/*');
> 65 | expect(await scenarioPage.getScenarioName.textContent()).toContain(scenarioName);
| ^
66 | expect(await scenarioPage.getScenarioDescription.textContent()).toContain(
67 | scenarioData.description
68 | );
at /app/tests/004-scenario-management.spec.ts:65:47
|
|
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/004-scenario-management.spec.ts#L1
1) [chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Retry #3 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 60000ms exceeded.
|
|
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/004-scenario-management.spec.ts#L65
1) [chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
Retry #3 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.textContent: Test timeout of 60000ms exceeded.
Call log:
- waiting for locator('.scenario-details-name .scenario-name')
63 | await createButton.click();
64 | await homePage.page.waitForURL('**/scenarios/*');
> 65 | expect(await scenarioPage.getScenarioName.textContent()).toContain(scenarioName);
| ^
66 | expect(await scenarioPage.getScenarioDescription.textContent()).toContain(
67 | scenarioData.description
68 | );
at /app/tests/004-scenario-management.spec.ts:65:47
|
|
[chromium] › 004-scenario-management.spec.ts:72:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario:
tests/004-scenario-management.spec.ts#L1
2) [chromium] › 004-scenario-management.spec.ts:72:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario
Test timeout of 60000ms exceeded.
|
|
[chromium] › 004-scenario-management.spec.ts:72:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario:
tests/pages/scenario-page-model.ts#L184
2) [chromium] › 004-scenario-management.spec.ts:72:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario
Error: locator.click: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByTitle('Modifier le scénario')
at pages/scenario-page-model.ts:184
182 |
183 | async openScenarioModalUpdate() {
> 184 | await this.getScenarioUpdateBtn.click();
| ^
185 | }
186 |
187 | async setScenarioDescription(description: string) {
at ScenarioPage.openScenarioModalUpdate (/app/tests/pages/scenario-page-model.ts:184:37)
at /app/tests/004-scenario-management.spec.ts:80:24
|
|
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/
|
|
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 (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 (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/
|
|
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/
|
|
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_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/
|
|
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 2.2m
|
|
Slow Test:
[firefox] › 009-rollingstock-editor.spec.ts#L1
[firefox] › 009-rollingstock-editor.spec.ts took 32.2s
|
|
Slow Test:
[chromium] › 009-rollingstock-editor.spec.ts#L1
[chromium] › 009-rollingstock-editor.spec.ts took 28.7s
|
|
Slow Test:
[webkit] › 002-project-management.spec.ts#L1
[webkit] › 002-project-management.spec.ts took 20.5s
|
|
🎭 Playwright Run Summary
36 failed
[chromium] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
[chromium] › 004-scenario-management.spec.ts:72:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario
[chromium] › 004-scenario-management.spec.ts:105:7 › Test if operationnal study : scenario creation workflow is working properly › Delete a scenario
[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] › 007-op-rollingstock-tab.spec.ts:47:7 › Verifying that all elements in the rolling stock tab are loaded correctly › should correctly select a rolling stock for operational study
[chromium] › 007-op-rollingstock-tab.spec.ts:92:7 › Verifying that all elements in the rolling stock tab are loaded correctly › should correctly modify a rolling stock for operational study
[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
[firefox] › 004-scenario-management.spec.ts:37:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
[firefox] › 004-scenario-management.spec.ts:72:7 › Test if operationnal study : scenario creation workflow is working properly › Update a scenario
[firefox] › 004-scenario-management.spec.ts:105:7 › Test if operationnal study : scenario creation workflow is working properly › Delete a scenario
[firefox] › 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
[firefox] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm ─────
[firefox] › 007-op-rollingstock-tab.spec.ts:47:7 › Verifying that all elements in the rolling stock tab are loaded correctly › should correctly select a rolling stock for operational study
[firefox] › 007-op-rollingstock-tab.spec.ts:92:7 › Verifying that all elements in the rolling stock tab are loaded correctly › should correctly modify a rolling stock for operational study
[firefox] › 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
[firefox] › 008-train-schedule.spec.ts:57:7 › Verifying that all elements in the train schedule are loaded correctly › should accurately filter the imported trains
[firefox] › 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
[firefox] › 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
[firefox] › 010-op-route-tab.spec.ts:125:7 › Verifying that all elements in the route tab are lo
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
integration-container-logs
Expired
|
179 KB |
|
|
integration-videos
Expired
|
109 MB |
|