Skip to content

front: implement results in the new interface for one simulation #7510

front: implement results in the new interface for one simulation

front: implement results in the new interface for one simulation #7510

Triggered via pull request July 5, 2024 15:36
Status Failure
Total duration 3m 26s
Artifacts

build.yml

on: pull_request
check_generated_railjson_sync
24s
check_generated_railjson_sync
check_railjson_generator
1m 46s
check_railjson_generator
check_commits
5s
check_commits
Check final newline
10s
Check final newline
check_integration_tests
1m 35s
check_integration_tests
check_osrd_schema
43s
check_osrd_schema
check_toml
9s
check_toml
check_infra_schema_sync
17s
check_infra_schema_sync
check_front_rtk_sync
0s
check_front_rtk_sync
check_core
0s
check_core
check_editoast_tests
0s
check_editoast_tests
check_editoast_lints
0s
check_editoast_lints
check_editoast_openapi
0s
check_editoast_openapi
check_gateway
0s
check_gateway
check_front
0s
check_front
integration_tests
0s
integration_tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
build
Process completed with exit code 1.
check_railjson_generator
The following actions uses Node.js version which is deprecated 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
The following actions uses Node.js version which is deprecated 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/