On Fri, Aug 29, 2008 at 1:25 PM, Peter Tröger <peter@troeger.eu> wrote:
Great idea, I did that by extending two existing test cases (ST_SUBMIT_IN_HOLD_DELETE and ST_SUBMIT_KILL_SIG). The test suite version is therefore now 1.6.0.
That's great!
- submit a job in hold state, - drmaa_control(TERMINATE) and drmaa_wait(), - assure that drmaa_wifaborted() == true, drmaa_wifexited() == drmaa_wifsignaled() == drmaa_wifcoredumped() == false,
- submit a long job (e.g. /bin/sleep 3600), - wait (polling) for it to start, - drmaa_control(TERMINATE) and drmaa_wait(), - assure that drmaa_wifsignaled() == true, drmaa_wifexited() == drmaa_wifaborted() == drmaa_wifcoredumped() == false,
wifexited() must be 0 for the first case, and !=0 for the second case.
Yep, my fault -- I was under the impression that signalled POSIX process doesn't have exit status which is obviously not true. Another thing. Now the following holds: wifaborted() == true if and only if wifexited() == false. Do we actually need wifaborted() then? When drmaa_wait() returns with success and wifexited() == false then we know that the process must have been aborted. Am I missing something? Or is it for this "we-have-no-idea-what-have-happend" state when aborted() == false && exited() == false? -- Piotr Domagalski