Skip to content

core: stdcm: implement variable stop durations #10921

core: stdcm: implement variable stop durations

core: stdcm: implement variable stop durations #10921

Triggered via pull request September 12, 2024 14:17
Status Failure
Total duration 13m 38s
Artifacts 2

build.yml

on: pull_request
Matrix: build
check_generated_railjson_sync
30s
check_generated_railjson_sync
check_railjson_generator
1m 45s
check_railjson_generator
check_commits
7s
check_commits
Check final newline
8s
Check final newline
check_integration_tests
1m 23s
check_integration_tests
check_osrd_schema
46s
check_osrd_schema
check_toml
4s
check_toml
check_infra_schema_sync
15s
check_infra_schema_sync
check_reuse_compliance
11s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 17 warnings, and 1 notice
StopTests.[1] true: core/src/test/kotlin/fr/sncf/osrd/stdcm/StopTests.kt#L626
org.opentest4j.AssertionFailedError: Expected <3000.0> with absolute tolerance <2.0>, actual <0.0>.
StopTests.[2] false: core/src/test/kotlin/fr/sncf/osrd/stdcm/StopTests.kt#L626
org.opentest4j.AssertionFailedError: Expected <3000.0> with absolute tolerance <2.0>, actual <0.0>.
check_core
Process completed with exit code 1.
[chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/003-study-management.spec.ts#L1
1) [chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Test timeout of 60000ms exceeded.
[chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/pages/study-page-model.ts#L110
1) [chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Error: locator.click: Test timeout of 60000ms exceeded. Call log: - waiting for getByTestId('add-study-button') - locator resolved to <div tabindex="0" role="button" class="study-card emp…>…</div> - attempting click action - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying at pages/study-page-model.ts:110 108 | 109 | async openStudyCreationModal() { > 110 | await this.getAddStudyBtn.click(); | ^ 111 | } 112 | 113 | async setStudyName(name: string) { at StudyPage.openStudyCreationModal (/app/tests/pages/study-page-model.ts:110:31) at /app/tests/003-study-management.spec.ts:37:21
[firefox] › 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: tests/010-op-route-tab.spec.ts#L1
2) [firefox] › 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 Test timeout of 60000ms exceeded.
[firefox] › 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: tests/pages/operational-studies-page-model.ts#L255
2) [firefox] › 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 Error: locator.waitFor: Test timeout of 60000ms exceeded. Call log: - waiting for getByTestId('missing-params-info') to be visible at pages/operational-studies-page-model.ts:255 253 | '' 254 | ); > 255 | await this.missingParamMessage.waitFor(); | ^ 256 | const actualMessage = await this.missingParamMessage.innerText(); 257 | expect(actualMessage).toContain(expectedMessage); 258 | } at OperationalStudiesPage.clickOnDeleteOPButtons (/app/tests/pages/operational-studies-page-model.ts:255:36) at /app/tests/010-op-route-tab.spec.ts:155:5
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_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 (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 (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_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_core
The following actions uses node12 which is deprecated and will be forced to run on node16: jwgmeligmeyling/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check_core
The following actions use a deprecated Node.js version and will be forced to run on node20: jwgmeligmeyling/[email protected]. 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
No files were found for the provided path: ./output/reports/spotbugs/*.xml. No results will be uploaded.
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] › 003-study-management.spec.ts#L1
[webkit] › 003-study-management.spec.ts took 27.4s
Slow Test: [webkit] › 002-project-management.spec.ts#L1
[webkit] › 002-project-management.spec.ts took 20.5s
Slow Test: [webkit] › 006-stdcm-page.spec.ts#L1
[webkit] › 006-stdcm-page.spec.ts took 15.7s
🎭 Playwright Run Summary
2 flaky [chromium] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study [firefox] › 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 84 passed (6.7m)

Artifacts

Produced during runtime
Name Size
integration-container-logs
236 KB
integration-videos
9.56 MB