Ticket #818 (closed bug: worksforme)

Opened 13 years ago

Last modified 13 years ago

packfile tests failing on amd64

Reported by: whiteknight Owned by:
Priority: normal Milestone:
Component: core Version: 1.3.0
Severity: medium Keywords: t packfile
Cc: Language:
Patch status: Platform:

Description

Test Summary Report
-------------------
t/pmc/packfile.t                     (Wstat: 256 Tests: 10 Failed: 0)
  Non-zero exit status: 1
  Parse errors: Bad plan.  You planned 34 tests but ran 10.
t/pmc/packfileannotations.t          (Wstat: 256 Tests: 1 Failed: 0)
  Non-zero exit status: 1
  Parse errors: Bad plan.  You planned 17 tests but ran 1.
t/pmc/packfileconstanttable.t        (Wstat: 256 Tests: 0 Failed: 0)
  Non-zero exit status: 1
  Parse errors: Bad plan.  You planned 14 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 23 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/packfilerawsegment.t           (Wstat: 256 Tests: 0 Failed: 0)
  Non-zero exit status: 1
  Parse errors: Bad plan.  You planned 2 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.
Files=248, Tests=8804, 59 wallclock secs ( 3.08 usr  0.64 sys + 66.12 cusr 25.39 csys = 95.23 CPU)
Result: FAIL

I've been getting these test failures for a few days. I normally ignore them because I can't seem to do anything about them on my machine (at least, last I checked I wasn't able to update the packfile examples used).

So three possible solutions:

  • If it's possible for me to update the packfiles used in the tests on my machine, (amd64+linux) I would love to learn how
  • Otherwise, if somebody else could update the packfiles in the tests, that would be much appreciated
  • If this isn't the issue and the packfiles in the tests are up to date, then I have some other weird bug.

Change History

Changed 13 years ago by whiteknight

More detail:

===(    4059;28  45/67  37/70  16/28  0/?   1/34 )======================Invalid charset number '30' specified
current instr.: '_pbc' pc 35 (t/pmc/testlib/packfile_common.pir:26)
called from Sub 'test_get_integer' pc 394 (t/pmc/packfile.t:103)
called from Sub 'main' pc 159 (t/pmc/packfile.t:29)
t/pmc/packfile.t ....................... Dubious, test returned 1 (wstat 256, 0x100)
Failed 24/34 subtests 
t/pmc/packfileannotation.t ............. ok                             
===(    4084;28  47/67  41/70  18/28   2/16   1/17 )====================Invalid charset number '30' specified
current instr.: 'test_unpack' pc 190 (t/pmc/packfileannotations.t:46)
called from Sub 'main' pc 141 (t/pmc/packfileannotations.t:26)
t/pmc/packfileannotations.t ............ Dubious, test returned 1 (wstat 256, 0x100)
Failed 16/17 subtests 
===(    4084;28  47/67  41/70  18/28   2/16 )===========================Invalid charset number '30' specified
current instr.: '_pbc' pc 35 (t/pmc/testlib/packfile_common.pir:26)
called from Sub 'test_sanity' pc 181 (t/pmc/packfileconstanttable.t:45)
called from Sub 'main' pc 132 (t/pmc/packfileconstanttable.t:32)
t/pmc/packfileconstanttable.t .......... Dubious, test returned 1 (wstat 256, 0x100)
Failed 14/14 subtests 
===(    4093;28  48/67  43/70  20/28   5/16   1/23 )====================Invalid charset number '30' specified
current instr.: '_pbc' pc 35 (t/pmc/testlib/packfile_common.pir:26)
called from Sub 'test_elements' pc 281 (t/pmc/packfiledirectory.t:65)
called from Sub 'main' pc 150 (t/pmc/packfiledirectory.t:28)
t/pmc/packfiledirectory.t .............. Dubious, test returned 1 (wstat 256, 0x100)
Failed 19/23 subtests 
===(    4097;29  49/67  43/70  20/28   5/16  0/3 )======================Invalid charset number '30' specified
current instr.: '_pbc' pc 35 (t/pmc/testlib/packfile_common.pir:26)
called from Sub 'test_sanity' pc 163 (t/pmc/packfilefixupentry.t:38)
called from Sub 'main' pc 132 (t/pmc/packfilefixupentry.t:27)
t/pmc/packfilefixupentry.t ............. Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/3 subtests 
===(    4097;29  49/67  43/70  20/28   5/16 )===========================Invalid charset number '30' specified
current instr.: '_pbc' pc 35 (t/pmc/testlib/packfile_common.pir:26)
called from Sub 'test_unpack' pc 145 (t/pmc/packfilefixuptable.t:36)
called from Sub 'main' pc 132 (t/pmc/packfilefixuptable.t:28)
t/pmc/packfilefixuptable.t ............. Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/3 subtests 
===(    4102;29  50/67  45/70  21/28   6/16 )===========================Invalid charset number '30' specified
current instr.: '_pbc' pc 35 (t/pmc/testlib/packfile_common.pir:26)
called from Sub 'test_elements' pc 154 (t/pmc/packfilerawsegment.t:35)
called from Sub 'main' pc 132 (t/pmc/packfilerawsegment.t:28)
t/pmc/packfilerawsegment.t ............. Dubious, test returned 1 (wstat 256, 0x100)
Failed 2/2 subtests 

Changed 13 years ago by whiteknight

  • status changed from new to closed
  • resolution set to worksforme

I went out to the store, and when I came back these tests were passing. Great. Closing this.

Note: See TracTickets for help on using tickets.