Skip to content
Setup a Slurm Cluster for tests

Setup a SLURM cluster in the GitHub CI for integration tests [MT-34] #3

Sign in to view logs

Setup a SLURM cluster in the GitHub CI for integration tests [MT-34]

Setup a SLURM cluster in the GitHub CI for integration tests [MT-34] #3

Triggered via pull request November 30, 2023 18:51
@lebricelebrice
synchronize #84
lebrice:setup_fake_cluster
Status Failure
Total duration 3m 19s
Artifacts –

slurm.yml

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

Annotations

5 errors and 5 warnings
testing (3.7)
Process completed with exit code 127.
testing (3.11)
Process completed with exit code 127.
testing (3.9)
The operation was canceled.
testing (3.10)
The operation was canceled.
testing (3.8)
Process completed with exit code 127.
testing (3.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: 1arp/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
testing (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: 1arp/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
testing (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: 1arp/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
testing (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: 1arp/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
testing (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: 1arp/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/