Skip to content

Update CI so oneapi 2023.2.0 is used #220

Update CI so oneapi 2023.2.0 is used

Update CI so oneapi 2023.2.0 is used #220

Triggered via pull request November 21, 2024 13:49
Status Success
Total duration 35m 0s
Artifacts

CI_sequential 4.yml

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

Annotations

4 warnings
build (gfortran, DEBUG, SEQUENTIAL, YES, NO)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@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 (gfortran, RELEASE, SEQUENTIAL, YES, NO)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@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 (ifort, DEBUG, SEQUENTIAL, YES, YES)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@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 (ifort, RELEASE, SEQUENTIAL, YES, YES)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/