Skip to content
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

Do more to check for unexpected mpiexec #215

Open
eirrgang opened this issue Dec 14, 2018 · 0 comments
Open

Do more to check for unexpected mpiexec #215

eirrgang opened this issue Dec 14, 2018 · 0 comments
Assignees
Labels

Comments

@eirrgang
Copy link
Collaborator

There are various ways a user could accidentally run a script in several processes, such as with mpiexec and for gmxapi not to notice (e.g. if mpi4py is not installed or is not triggered because the work graph does not require parallelism). There should be some heuristics and precautions we can apply to minimize the chance of running multiple copies of the same work graph in the same directory at the same time, such as checking for environment variables and using lock files.

For convenience, if a lock file doesn't get cleaned up from a failed job, we can add a force_remove_lock=true option to run()

@eirrgang eirrgang added the bug label Dec 14, 2018
@eirrgang eirrgang self-assigned this Dec 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant