Skip to content

fix: an issue of established f-m connections being duplicated in the … #9441

fix: an issue of established f-m connections being duplicated in the …

fix: an issue of established f-m connections being duplicated in the … #9441

Triggered via push December 19, 2024 22:52
Status Failure
Total duration 6h 0m 48s
Billable time 55m
Artifacts

ci_tests.yml

on: push
semantic_pull_request
1s
semantic_pull_request
is_not_draft_pull_request
3s
is_not_draft_pull_request
Matrix: cpu_builds
Matrix: check_code_style_and_documentation
Matrix: cuda_builds
if_not_unassigned_pull_request
0s
if_not_unassigned_pull_request
are_submodules_in_sync
8s
are_submodules_in_sync
baseline_log
3s
baseline_log
code_coverage  /  build_test_deploy
54m 34s
code_coverage / build_test_deploy
run_integrated_tests  /  build_test_deploy
36m 23s
run_integrated_tests / build_test_deploy
check_that_all_jobs_succeeded
0s
check_that_all_jobs_succeeded
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Pangea 3 CUDA (AlmaLinux 8.8, gcc 9.4.0, open-mpi 4.1.2, cuda 11.5.0, openblas 0.3.10) / build_test_deploy
The job running on runner streak2-3 has exceeded the maximum execution time of 360 minutes.
check_that_all_jobs_succeeded
Process completed with exit code 1.
semantic_pull_request
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636