On Thu, Jul 2, 2009 at 4:03 PM, Michael G Schwern<schw...@pobox.com> wrote: > This is a quick release to sync with perl so 5.10.1 can release with a stable > version number. It does NOT include the subtest() code in 0.89_01 (don't > worry, it'll be back).
The attached patch does two things:
1.) Copy and paste the skip logic from t/fork.t to
t/Builder/fork_with_new_stdout.t for platforms that don't have
$Config{d_fork} or pseudo-fork.
2.) Now works a bit harder to suppress (most of) the SS$_ABORT
messages on VMS. Passing -Mvmsish=hushed on the command line works
for one-liners, but not for separate programs. I should know why that
is, but it's not coming to mind right now. In any case, there is
still some chatter [1], but fixing that would mean prepending the
pragma to all the .plx files.
Tests run with:
$ perl -v
This is perl, v5.11.0 (GitLive-blead-1508-g24054a1*) built for VMS_IA64-ithread
[1]
ok 256 - exit map test for 255
# Done.
ok 257 - death.plx exited with 4 (expected 4)
%SYSTEM-F-ABORT, abort
%SYSTEM-F-ABORT, abort
ok 258 - too_few.plx exited with 4 (expected 4)
ok 259 - require.plx exited with 0 (expected 0)
%SYSTEM-F-ABORT, abort
%SYSTEM-F-ABORT, abort
ok 260 - too_few_fail.plx exited with 4 (expected 4)
%SYSTEM-F-ABORT, abort
%SYSTEM-F-ABORT, abort
ok 261 - five_fail.plx exited with 4 (expected 4)
ok 262 - pre_plan_death.plx exited with 4 (expected non-zero)
ok 263 - death_with_handler.plx exited with 4 (expected 4)
%SYSTEM-F-ABORT, abort
%SYSTEM-F-ABORT, abort
ok 264 - extras.plx exited with 4 (expected 4)
ok 265 - success.plx exited with 0 (expected 0)
%SYSTEM-F-ABORT, abort
%SYSTEM-F-ABORT, abort
ok 266 - two_fail.plx exited with 4 (expected 4)
ok 267 - death_in_eval.plx exited with 0 (expected 0)
ok 268 - last_minute_death.plx exited with 4 (expected 4)
%SYSTEM-F-ABORT, abort
%SYSTEM-F-ABORT, abort
ok 269 - one_fail.plx exited with 4 (expected 4)
ok 270 - exit.plx exited with 4 (expected 4)
vms_test_more.patch
Description: Binary data
