[GE issues] [Issue 2814] New - Removing a job causes DRMAA to behave in a non-compliant way

szalik piotr.domagalski at fedstage.com
Mon Dec 1 17:25:37 GMT 2008


http://gridengine.sunsource.net/issues/show_bug.cgi?id=2814
                 Issue #|2814
                 Summary|Removing a job causes DRMAA to behave in a non-complia
                        |nt way
               Component|gridengine
                 Version|6.2
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|drmaa
             Assigned to|dagru
             Reported by|szalik






------- Additional comments from szalik at sunsource.net Mon Dec  1 09:25:37 -0800 2008 -------
Hi,

According to the latest DRMAA 1.0 specification [1] and also discussions on the
mailing list [2] drmaa_wifaborted() should be true only if the job was cancelled
*before* entering the running state.

But in SGE drmaa_wifaborted() is true also when the job is deleted (qdel) or
terminated with DRMAA itself (DRMAA_CONTROL_TERMINATE).

According to my discussions with DRMAA authors the return status from
drmaa_wait() in case of removing an already running job should reflect the fact
that the job is signalled (drmaa_wifsignaled() = true).

[1] From http://www.ogf.org/documents/GFD.133.pdf:

drmaa_wifaborted(...)
Evaluates into 'aborted', a non-zero value if 'stat'
was returned for a job that ended before entering the running state.

[2] http://www.ogf.org/pipermail/drmaa-wg/2008-August/thread.html

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=36&dsMessageId=90608

To unsubscribe from this discussion, e-mail: [issues-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list