Some thoughts on drmaa_wifaborted vs. DRMAA spec
(had some subscription problems, reposting it) Hi all! According to the spec: drmaa_wifaborted: Evaluates into 'aborted', a non-zero value if 'stat' was returned for a job that ended before entering the running state. so aborted = true IFF the job was deleted before getting into DRMAA_PS_RUNNING? If so, then it seems that SGE's implementation is buggy, because it sets aborted for jobs terminated after having entered the running state. On the other hand [1], if drmaa_wifaborted() works this way and drmaa_wifexited(): Evaluates into 'exited' a non-zero value if stat was returned for a job that either failed after running or finished after running (see section 2.6). More detailed diagnosis can be provided by means of drmaa_wexitstatus(). Then what should I get when the job was terminated (by DRMAA) within running state? aborted = false, exited = true? What about exit status then? [1] I'm asking this question, because I thought for a long time that this SGE's behavior was according to the specification. -- Piotr Domagalski
participants (1)
-
Piotr Domagalski