t/pmc/packfile.t: Warning about invalid Parrot bytecode file

Andy Dougherty doughera at lafayette.edu
Thu Aug 5 17:41:36 UTC 2010


On Wed, 4 Aug 2010, James E Keenan wrote:

> Tonight, for the second time since our last release, when I did 'svn up',
> configured, built and tested on Darwin/PPC, I got failures in the
> t/pmc/packfile*.t tests:
> 
> t/pmc/packfile.t                          (Wstat: 256 Tests: 11 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 37 tests but ran 11.
> t/pmc/packfileconstanttable.t             (Wstat: 256 Tests: 0 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 16 tests but ran 0.
> t/pmc/packfiledirectory.t                 (Wstat: 256 Tests: 4 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 20 tests but ran 4.
> t/pmc/packfilefixupentry.t                (Wstat: 256 Tests: 0 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 3 tests but ran 0.
> t/pmc/packfilefixuptable.t                (Wstat: 256 Tests: 0 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 3 tests but ran 0.
> t/pmc/packfilerawsegment.t                (Wstat: 256 Tests: 0 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: Bad plan.  You planned 7 tests but ran 0.

This is the same as TT #1712.  The tests are simply wrong.

-- 
    Andy Dougherty		doughera at lafayette.edu



More information about the parrot-dev mailing list