[Iplant-api-dev] API v1 JOB states

[Cornel Ghiban]

Hi Rion,

 From what I'm seeing, not setting archive in v1, will not archive the output 
and the end status if FINISHED. eg job 39185

Thanks,
Cornel

On 01/10/2014 07:34 PM, Rion Dooley wrote:
> If you set archived to true in your job submission, the job should archive. It should also archive by default if you don’t specify anything. The job should pass through the FINISHED state and, if archiving, go on to ARCHIVING_FINISHED, though it may not get there if you exceed your wall time.
>
> This is all Foundation specific. Documentation on the behavior in Agave is available at http://agaveapi.co/job-management/
>
> --
> Rion
>
>
>
>
> On Jan 10, 2014, at 6:16 PM, Cornel Ghiban <ungreen at gmail.com<mailto:ungreen at gmail.com>> wrote:
>
> Hi,
>
> I'm having some trouble with the jobs status.
> If I tell it to archive am I supposed to ever see status FINISHED (and then ARCHIVING_FINISHED)? I thought in this case I should only see ARCHIVING_FINISHED.
>
> Is there a wiki page about this?
>
> Thanks,
> Cornel
> _______________________________________________
> Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org<mailto:Iplant-api-dev at iplantcollaborative.org>
> List Info and Archives: http://mail.iplantcollaborative.org/mailman/listinfo/iplant-api-dev
> One-click Unsubscribe: http://mail.iplantcollaborative.org/mailman/options/iplant-api-dev/dooley%40tacc.utexas.edu?unsub=1&unsubconfirm=1
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20140110/5f71a214/attachment.html