[DRMAA-WG] normal exit status causes drmaa_wifaborted

Tim Harsch harsch1 at llnl.gov
Wed Mar 28 12:24:19 CDT 2007


I don't understand why causing a simple non-zero exit status is causing 
drmaa_wifaborted to be set.

The easiest way for me to demo this is to change line 38 of 
t/08_posix_tests.t of the Schedule::DRMAAc CPAN module to be
my $remote_cmd = "csh -c 'exit 1'";

And then running "make test TEST_VERBOSE=1", which would produce:
<SNIP>
ok 12 - drmaa_wait says jobid did not change?
#     Failed test (t/08_posix_tests.t at line 83)
not ok 13 - drmaa_wait should say there is more info available in POSIX 
funcs
ok 15 - drmaa_wifaborted error?
#     Failed test (t/08_posix_tests.t at line 90)
not ok 16 - normal job should not abort.
ok 17 - drmaa_wifexited returned 3 of 3 args
ok 18 - drmaa_wifexited error?
#     Failed test (t/08_posix_tests.t at line 97)
not ok 19 - normal job should exit.
<SNIP>

I've attached test 8 to this email, in case you want to see how the calls 
are made in Perl.

Any ideas?

Thanks,
Tim Harsch 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 08_posix_tests.t
Type: application/octet-stream
Size: 6179 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/drmaa-wg/attachments/20070328/cbe51a16/attachment.obj 


More information about the drmaa-wg mailing list