-
Notifications
You must be signed in to change notification settings - Fork 202
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
change default job backend to Slurm + deprecate support for using GC3Pie as job backend #4565
Comments
It seems that the current implementation of the Slurm backend does not support the experimental easystack feature. When compiling easystacks compilation jobs are resubmitted without dependencies on previous entries of the easystack. Consider for instance the easystack file: easyconfigs:
- foss-2024.05.eb
- HDF5-1.14.3-gompi-2023b.eb Jobs for I am mentioning the issue here because easystacks seem like a good use case for parallel compilation jobs. |
@gkaf89 I looked into that in #4558 (comment) but I would need to find time to implement |
- The GC3Pie back-end for job management that has been the default so far is no longer actively supported. Use the Slurm back-end as default instead. - Add deprecation message when the GC3Pie class is instantiated. Issue: easybuilders#4565
- The GC3Pie back-end for job management that has been the default so far is no longer actively supported. Use the Slurm back-end as default instead. - Add deprecation message when the GC3Pie class is instantiated. Issue: easybuilders#4565
- The GC3Pie back-end for job management that has been the default so far is no longer actively supported. Use the Slurm back-end as default instead. - Add deprecation message when the GC3Pie class is instantiated. Issue: easybuilders#4565
- The GC3Pie back-end for job management that has been the default so far is no longer actively supported. Use the Slurm back-end as default instead. - Add deprecation message when the GC3Pie class is instantiated. Issue: easybuilders#4565
No description provided.
The text was updated successfully, but these errors were encountered: