Tim, Looks like something localized to the Perl binding or your configuration. I did the same test on the Java language binding, which is also based on the C binding, and it worked fine for me. Output below, program attached. Could the problem be that you're sending the full command line as the remote command and "1" as the args, instead of "csh" as the remote command and "-c", "'exit 1'" as the args? What is the meaning of setting the args to "1"? --- % java -cp /sge/lib/drmaa.jar:. -d64 Test Exited: true Aborted: false Signaled: false --- Daniel Tim Harsch wrote:
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 ------------------------------------------------------------------------
-- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg