-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release 2.5.11 #95
Comments
FRCE run failed for me, with multiple rules failing due to this error:
Unsure why the pipeline is not detecting FRCE and appears to think it's still on Biowulf. @kelly-sovacool is running a test on FRCE to determine if it's a user issue or if it's something more systemic. |
My test on FRCE worked 🤔 RENEE Fri Jan 19 11:26:54 EST 2024
Running pipeline with the following parameters:
b /mnt/projects/CCBR-Pipelines,/mnt/projects/CCBR-Pipelines/Pipelines/RENEE/renee-dev-sovacool/.tests,/scratch/cluster_scratch/sovacoolkl/renee_test_v2.5.11,/scratch/cluster_scratch/sovacoolkl
c /scratch/cluster_scratch/sovacoolkl/renee_test_v2.5.11/.singularity
e slurm
h frce
j pl:renee
o /scratch/cluster_scratch/sovacoolkl/renee_test_v2.5.11
t /scratch/cluster_scratch/sovacoolkl/renee_test_v2.5.11
w --nowait
[Fri Jan 19 11:26:55 EST 2024] Pipeline submitted to cluster.
Master Job ID: 30547456
JobID Partition Timelimit Elapsed NodeList Submit Start End State ExitCode
------------ ---------- ---------- ---------- --------------- ------------------- ------------------- ------------------- ---------- --------
30547456 norm 4-00:00:00 00:49:17 cn062 2024-01-19T11:26:55 2024-01-19T11:27:00 2024-01-19T12:16:17 FAILED 1:0 |
Oh, it's because I set |
issue with permissions #101 fixed. FRCE run completed successfully! |
closed by #102 |
Steps
Test: Biowulf
Deployment:
Status:
Test: FRCE
Deployment:
Status:
The text was updated successfully, but these errors were encountered: