op/sprintf2.t is failing because of limitations in parsing the TAP output from binaries

[toddr]

currently op/sprintf2.t is failing because of tests out of sequence:

    ok 1255 - sprintf("%0-+04d",1)
    ok 1256 - sprintf("%0- 4d",1)
    ok 1257 - sprintf("%0- -4d",1)
    ok 12# Compiling: >  /usr/local/cpanel/3rdparty/perl/524/bin/perl /usr/local/cpanel/3rdparty/perl/524/bin/perlcc  -o op/sprintf2.subtest.1356.bin op/sprintf2.subtest.1356.t 2>&1
    58 - sprintf("%0- +4d",1)
    ok 1259 - sprintf("%0-  4d",1)
    ok 1260 - sprintf("%0- 04d",1)

It looks like this is happening because STDERR and STDOUT are being mixed together.

This is likely a bug fixed near:
t/lib/TestCompile.pm

    my $harness = TAP::Harness->new( \%args );
    my $res     = $harness->runtests($bin_file);

Though the problem may be in STDERR redirection (or lack of?) in test.pl

Currently sprintf2.t is passing so it's not a huge deal.