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.

Sign up for GitHub

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

Jump to bottom

Jug sleep-until exits too early when using barrier #71

Closed
luispedro opened this issue Apr 2, 2018 · 0 comments
Closed

Jug sleep-until exits too early when using barrier #71

luispedro opened this issue Apr 2, 2018 · 0 comments

Comments

@luispedro
Copy link
Owner

Reported on the jug-users mailing list:

I have a code that requires multiple merge points. At these merge points, a file is written, and the next section of the code uses that file. To address this, I've used jug.barrier(). Since I would like to submit this as a batch job, I created a script run_jug.sh, which will run multiple jug processes on a single node. In that script, I use sleep-until to prevent the batch job from ending early. The problem I'm encountering is that sleep-until seems to be satisfied when all jug processes hit the first jug.barrier(), and as such the batch job ends early.

I confirm that this is a bona fides bug.
@zhafen zhafen mentioned this issue Aug 24, 2018
Closed
luispedro added a commit that referenced this issue Jan 31, 2020
@luispedro
RLS Version 2.0.0rc0
4492ae4 
The big changes are failed tasks (contributed by @unode).

Also, environmental variables are now always checked and creating a file
called `__jug_please_stop.txt` will stop a `jug execute` run in a clean
way.

Full ChangeLog
    * jug.backend.base_store has 1 new method `listlocks`
    * jug.backend.base_lock has 2 new methods `fail` and `is_failed`
    * Add 'jug execute --keep-failed' to preserve locks on failing tasks.
    * Add 'jug cleanup --failed-only' to remove locks from failed tasks
    * 'jug status' and 'jug graph' now display failed tasks
    * Check environmental exit variables by default (suggested by Renato Alves, issue #66)
    * Fix 'jug sleep-until' in the presence of barrier() (issue #71)
luispedro added a commit that referenced this issue Jan 31, 2020
@luispedro
RLS Version 2.0.0rc0
f1a0833 
The big changes are failed tasks (contributed by @unode).

Also, environmental variables are now always checked and creating a file
called `__jug_please_stop.txt` will stop a `jug execute` run in a clean
way.

Full ChangeLog
    * jug.backend.base_store has 1 new method `listlocks`
    * jug.backend.base_lock has 2 new methods `fail` and `is_failed`
    * Add 'jug execute --keep-failed' to preserve locks on failing tasks.
    * Add 'jug cleanup --failed-only' to remove locks from failed tasks
    * 'jug status' and 'jug graph' now display failed tasks
    * Check environmental exit variables by default (suggested by Renato Alves, issue #66)
    * Fix 'jug sleep-until' in the presence of barrier() (issue #71)
luispedro added a commit that referenced this issue Feb 21, 2020
@luispedro
RLS Version 2.0.0
8eb8210 
The big changes are failed tasks (contributed by @unode).

Also, environmental variables are now always checked and creating a file
called `__jug_please_stop.txt` will stop a `jug execute` run in a clean
way.

Full ChangeLog
    * jug.backend.base_store has 1 new method `listlocks`
    * jug.backend.base_lock has 2 new methods `fail` and `is_failed`
    * Add 'jug execute --keep-failed' to preserve locks on failing tasks.
    * Add 'jug cleanup --failed-only' to remove locks from failed tasks
    * 'jug status' and 'jug graph' now display failed tasks
    * Check environmental exit variables by default (suggested by Renato Alves, issue #66)
    * Fix 'jug sleep-until' in the presence of barrier() (issue #71)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@luispedro