Skip to content
GEOS CI

ci: add the possitility to use other build generators than ninja inside the ci #6799

Sign in to view logs

ci: add the possitility to use other build generators than ninja inside the ci

ci: add the possitility to use other build generators than ninja inside the ci #6799

Triggered via pull request August 14, 2024 08:23
@AlgianeAlgiane
synchronize #3276
feature/algiane/build-generator-option-in-ci
Status Failure
Total duration 1h 32m 26s
Billable time 46m
Artifacts –

ci_tests.yml

on: pull_request
semantic_pull_request
2s
semantic_pull_request
is_not_draft_pull_request
4s
is_not_draft_pull_request
Matrix: cpu_builds
Matrix: check_code_style_and_documentation
Matrix: cuda_builds
if_not_unassigned_pull_request
3s
if_not_unassigned_pull_request
are_submodules_in_sync
10s
are_submodules_in_sync
baseline_log
4s
baseline_log
code_coverage  /  build_test_deploy
45m 24s
code_coverage / build_test_deploy
run_integrated_tests  /  build_test_deploy
40m 54s
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

2 errors
Ubuntu CUDA (20.04, clang 10.0.0 + gcc 9.4.0, open-mpi 4.0.3, cuda-11.8.89) / build_test_deploy
Process completed with exit code 8.
check_that_all_jobs_succeeded
Process completed with exit code 1.