Skip to content

FPM

FPM #23

Triggered via pull request November 21, 2023 22:31
@jchristophersonjchristopherson
synchronize #18
FPM
Status Failure
Total duration 1m 17s
Artifacts

fpm.yml

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

Annotations

4 errors and 4 warnings
gcc-build (ubuntu-latest, 10)
Process completed with exit code 134.
gcc-build (macos-11, 10)
Process completed with exit code 4.
intel-build
Process completed with exit code 134.
msys2-build
Process completed with exit code 127.
gcc-build (ubuntu-latest, 10)
The following actions uses node12 which is deprecated and will be forced to run on node16: fortran-lang/setup-fpm@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
gcc-build (macos-11, 10)
The following actions uses node12 which is deprecated and will be forced to run on node16: fortran-lang/setup-fpm@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
intel-build
The following actions uses node12 which is deprecated and will be forced to run on node16: fortran-lang/setup-fpm@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
msys2-build
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/