Skip to content
Investigate Linux compilation issues

ci: investigate why extensions are not compiled #1

Sign in to view logs

ci: investigate why extensions are not compiled

ci: investigate why extensions are not compiled #1

Triggered via pull request July 23, 2024 07:08
@dacorvodacorvo
opened #253
investigate_ci_compilation_issues
Status Failure
Total duration 4m 17s
Artifacts –

test-compilation.yml

on: pull_request
Matrix: investigate
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
investigate (cpu)
Process completed with exit code 1.
investigate (cuda)
Process completed with exit code 1.
investigate (cpu)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
investigate (cpu)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
investigate (cuda)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
investigate (cuda)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/