Re: [perl.git] branch blead, updated. v5.13.2-96-ga642fc5

> In perl.git, the branch blead has been updated
> 
> <http://perl5.git.perl.org/perl.git/commitdiff/a642fc51b9c225f75f859da6a69df0b4ac81d396?hp=ded2eedcb4ea5645092eea71df32e0f737b89d90>
> 
> - Log -----------------------------------------------------------------
> commit a642fc51b9c225f75f859da6a69df0b4ac81d396

>     Fixed up Test-Harness tests to work under core. There are still three outstanding will ask AndyA to investigate

As a policy, I don't like this. I'd much prefer non-integration or explicit
TODOs or SKIPs instead of known tests failing.

Known tests failing are bad because:

1: We end up with F smoke reports, which we then either
   a: need to look at to determine that they are "known" failures
   b: ignore, because there are "known" failures, which hides any real new
      failures that happen at the same time
2: In the future, it makes bisecting harder. As tests fail, and it's not
   obvious why.


I'm minded to make this lot skip:

../cpan/Test-Harness/t/regression.t                             (Wstat: 8192 Tests: 7204 Failed: 32)
  Failed tests:  1473, 1476, 2899, 2902, 5131, 5133-5135
                5138, 5143-5144, 5148-5150, 5152-5153, 5156-5157
                6445, 6447-6449, 6452, 6457-6458, 6462-6464
                6466-6467, 6470-6471
  Non-zero exit status: 32
../cpan/Test-Harness/t/source_handler.t                         (Wstat: 1536 Tests: 87 Failed: 6)
  Failed tests:  13-14, 35-36, 84-85
  Non-zero exit status: 6
  Parse errors: Bad plan.  You planned 123 tests but ran 87.
../cpan/Test-Harness/t/taint.t                                  (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1


until we have a proper solution.

Nicholas Clark

• Re: [perl.git] branch blead, updated. v5.13.2-96-ga642fc5 by Nicholas Clark
• Re: [perl.git] branch blead, updated. v5.13.2-96-ga642fc5 by Nicholas Clark