[Swift-devel] Extra jobs in coaster runs?

[Mihael Hategan]

On Sun, 2011-11-13 at 20:00 -0600, Michael Wilde wrote:
> 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?

The cleanup jobs are actually sent as batch jobs, so swift doesn't wait
for them.

Mihael