[Swift-devel] Extra jobs in coaster runs?

[Michael Wilde]

Mihael, ALl,

I noticed in hunting down the beagle bug that we're getting "spurious" jobs submitted, seemingly at the end of a coaster run.  FOr example, after running 1000 simple cats, I see these two extra in cleanup state: in the run below 51903 and 51905 were the "main" job that ran my app() calls.  1 app call for 51903, 1000 for 51905.

Then as these scripts terminate, it seems that some weird (cleanup)? job gets sent, with the jobname "cog-000000".

If that is indeed cleanup, any idea why it gets sent as a separate job instead of doing the cleanup action as part of the existing coaster block?  In that case can we avoid having to wait on another queued job to finish the script?

- Mike

login1$ qstat -u wilde

sdb: 
                                                                         Req'd  Req'd   Elap
Job ID               Username Queue    Jobname          SessID NDS   TSK Memory Time  S Time
-------------------- -------- -------- ---------------- ------ ----- --- ------ ----- - -----
519103.sdb           wilde    developm Block-1114-3601   19725     3  --    --  00:02 C 00:00
519104.sdb           wilde    developm cog-000000        18568     3  --    --  00:00 C 00:00
519105.sdb           wilde    developm Block-1114-3901   20898     3  --    --  00:02 C 00:00
519106.sdb           wilde    developm cog-000000        21367     3  --    --  00:00 C 00:00
login1$ 


-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory