Bug 160 – job dependent upon array stuck in UserHold state

Bug 160 - job dependent upon array stuck in UserHold state

Summary:

job dependent upon array stuck in UserHold state

Status:	NEW

Product:	TORQUE
Component:	pbs_server
Version:	2.5.x
Platform:	PC Linux

Importance:	P5 critical
Assigned To:	David Beer

URL:

Depends on:	178
Blocks:
	Show dependency tree / graph

Reported:	2011-10-06 10:41 MDT by Brian Andrus
Modified:	2012-04-26 00:09 MDT (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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
depend=afterokarray:$jid[]


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
with:

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`