Bug 160 - job dependent upon array stuck in UserHold state
: job dependent upon array stuck in UserHold state
Status: NEW
Product: TORQUE
: 2.5.x
: PC Linux
: P5 critical
Assigned To: David Beer
: 178
  Show dependency treegraph
Reported: 2011-10-06 10:41 MDT by Brian Andrus
Modified: 2012-04-26 00:09 MDT (History)
2 users (show)

See Also:



You need to log in before you can comment on or make changes to this bug.

Description Brian Andrus 2011-10-06 10:41:21 MDT
We are trying to run a job after an array job completes successfully.

jid=$(echo 'echo $PBS_ARRAYID;sleep 60'|qsub -l walltime=00:01:00 -l procs=2 -t
0-10);echo 'hostname'|qsub -l walltime=00:01:00 -l procs=2 -W

The array job completes, but the dependent job ends up in a ‘UserHold’ state.

Shouldn’t the dependent job move from the UserHold state to no hold and
eligible once the array jobs complete??
Comment 1 rhys.hill 2012-04-26 00:09:42 MDT
This works for me with torque 4.0.1 and the patch from Bug 178. I'm testing

ID1=`qsub -t 1-2                               ./stage1.sh`
ID2=`qsub        -W depend=afterokarray:${ID1} ./stage2.sh`
ID3=`qsub -t 1-2 -W depend=afterok:${ID2}      ./stage3.sh`