Skip Menu |

This queue is for tickets about the KinoSearch CPAN distribution.

Report information
The Basics
Id: 39689
Status: resolved
Priority: 0/
Queue: KinoSearch

People
Owner: Nobody in particular
Requestors: aar [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.163
Fixed in: (no value)



Subject: Test #101 fails on Debian PPC
# uname -a Linux 2.6.18-6-powerpc #1 Tue Aug 19 04:51:39 UTC 2008 ppc GNU/Linux t/101-simple_template_io......NOK 2 # Failed test 'signed byte' # in t/101-simple_template_io.t at line 21. # Structures begin differing at: # $got->[0] = '128' # $expected->[0] = '-128' t/101-simple_template_io......ok 7/13# Looks like you failed 1 test of 13. t/101-simple_template_io......dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 2 Failed 1/13 tests, 92.31% okay t/102-strings_template_io.....ok t/103-repeats_template_io.....NOK 2 # Failed test 'b2' # in t/103-repeats_template_io.t at line 20. # Structures begin differing at: # $got->[0] = '128' # $expected->[0] = '-128' t/103-repeats_template_io.....NOK 4 # Failed test 'b131' # in t/103-repeats_template_io.t at line 20. # Structures begin differing at: # $got->[0] = '128' # $expected->[0] = '-128' t/103-repeats_template_io.....NOK 6 # Failed test 'b149' # in t/103-repeats_template_io.t at line 20. # Structures begin differing at: # $got->[0] = '128' # $expected->[0] = '-128' t/103-repeats_template_io.....NOK 8 # Failed test 'b256' # in t/103-repeats_template_io.t at line 20. # Structures begin differing at: # $got->[0] = '128' # $expected->[0] = '-128' # Looks like you failed 4 tests of 18. t/103-repeats_template_io.....dubious Test returned status 4 (wstat 1024, 0x400) DIED. FAILED tests 2, 4, 6, 8 Failed 4/18 tests, 77.78% okay
FWIW, I'm seeing this same error under s390x (SLES 10) using KinoSearch-0.20_051.
From: ianburrell [...] gmail.com
This also fails in the same way when building 0.163 for Fedora on PPC. The build logs showing the test failure are in http://koji.fedoraproject.org/koji/getfile?taskID=1127120&name=build.log
This problem arose because of an incorrect assumption that "char" was a signed type. It has now been fixed in both the 0.1x stable and 0.3x devel branches.