-
Notifications
You must be signed in to change notification settings - Fork 9
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
Adds lock to FM provider #882
Conversation
… running in cluster mode
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## vara-dev #882 +/- ##
=========================================
Coverage 66.49% 66.49%
=========================================
Files 344 344
Lines 27935 27938 +3
=========================================
+ Hits 18575 18578 +3
Misses 9360 9360 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Florian Sattler <[email protected]>
When running experiments on slurm, it can happen that multiple nodes fetch the feature model repository at the same time. As nodes may use a shared feature model repository (E.g. on /scratch/) this can lead to issues. This is no issue if the feature model repository is already up-to-date, however if there are any upstream changes this leads to errors in the fetch on some nodes and subsequent failure of the slurm jobs. --------- Co-authored-by: Lukas Abelt <[email protected]> Co-authored-by: Florian Sattler <[email protected]>
Adds a lock to the feature model provider.
When running experiments on slurm, it can happen that multiple nodes fetch the feature model repository at the same time. As nodes may use a shared feature model repository (E.g. on
/scratch/
) this can lead to issues.This is no issue if the feature model repository is already up-to-date, however if there are any upstream changes this leads to errors in the fetch on some nodes and subsequent failure of the slurm jobs.