Re: Poke rpm package and test failures on i586, armv7l, ppc64 and ppc64le

[Jose E. Marchesi]

        Any ideas what could be causing these test failures?
        
    I will take a look, and file bugs accordingly.

Ok, the 65 test failures in i586 can be reproduced building a 32-bit
poke and running the testsuite.  There is something wrong in the
handling of unsigned integers in 32-bit (I just filed a bugzilla for
this):

FAIL: poke.map/maps-uint-17.pk output pattern test
FAIL: poke.map/maps-uint-20.pk output pattern test
FAIL: poke.map/maps-uint-22.pk output pattern test
FAIL: poke.map/maps-uint-23.pk output pattern test
FAIL: poke.map/maps-uint-24.pk output pattern test
FAIL: poke.map/maps-uint-25.pk output pattern test
FAIL: poke.map/maps-uint-26.pk output pattern test
FAIL: poke.map/maps-uint-27.pk output pattern test
FAIL: poke.map/maps-uint-28.pk output pattern test
FAIL: poke.map/maps-uint-29.pk output pattern test
FAIL: poke.map/maps-uint-30.pk output pattern test
FAIL: poke.map/maps-uint-31.pk output pattern test
FAIL: poke.map/maps-uint-32.pk output pattern test
FAIL: poke.map/maps-uint-33.pk output pattern test
FAIL: poke.map/maps-uint-34.pk output pattern test
FAIL: poke.map/maps-uint-35.pk output pattern test
FAIL: poke.map/maps-uint-36.pk output pattern test
FAIL: poke.map/maps-uint-37.pk output pattern test
FAIL: poke.map/maps-uint-38.pk output pattern test
FAIL: poke.map/maps-uint-39.pk output pattern test
FAIL: poke.map/maps-uint-40.pk output pattern test
FAIL: poke.map/maps-uint-47.pk output pattern test
FAIL: poke.map/maps-uint-48.pk output pattern test
FAIL: poke.map/maps-uint-49.pk output pattern test
FAIL: poke.map/maps-uint-50.pk output pattern test
FAIL: poke.map/maps-uint-51.pk output pattern test
FAIL: poke.map/maps-uint-52.pk output pattern test
FAIL: poke.map/maps-uint-53.pk output pattern test
FAIL: poke.map/maps-uint-54.pk output pattern test
FAIL: poke.map/maps-uint-write-39.pk output pattern test
FAIL: poke.map/maps-uint-write-40.pk output pattern test
FAIL: poke.map/maps-uint-write-41.pk output pattern test
FAIL: poke.map/maps-uint-write-42.pk output pattern test
FAIL: poke.map/maps-uint-write-43.pk output pattern test
FAIL: poke.map/maps-uint-write-44.pk output pattern test
FAIL: poke.map/maps-uint-write-45.pk output pattern test
FAIL: poke.map/maps-uint-write-46.pk output pattern test
FAIL: poke.map/maps-uint-write-47.pk output pattern test
FAIL: poke.map/maps-uint-write-48.pk output pattern test
FAIL: poke.map/maps-uint-write-49.pk output pattern test
FAIL: poke.map/maps-uint-write-50.pk output pattern test
FAIL: poke.map/maps-uint-write-51.pk output pattern test
FAIL: poke.map/maps-uint-write-52.pk output pattern test
FAIL: poke.map/maps-uint-write-53.pk output pattern test
FAIL: poke.map/maps-uint-write-54.pk output pattern test
FAIL: poke.map/maps-uint-write-55.pk output pattern test
FAIL: poke.map/maps-uint-write-56.pk output pattern test
FAIL: poke.map/maps-uint-write-57.pk output pattern test
FAIL: poke.map/maps-uint-write-58.pk output pattern test
FAIL: poke.map/maps-uint-write-59.pk output pattern test
FAIL: poke.map/maps-uint-write-60.pk output pattern test
FAIL: poke.map/maps-uint-write-61.pk output pattern test
FAIL: poke.map/maps-uint-write-62.pk output pattern test
FAIL: poke.map/maps-uint-write-63.pk output pattern test
FAIL: poke.map/maps-uint-write-64.pk output pattern test
FAIL: poke.map/maps-uint-write-65.pk output pattern test
FAIL: poke.map/maps-uint-write-66.pk output pattern test
FAIL: poke.map/maps-uint-write-67.pk output pattern test
FAIL: poke.map/maps-uint-write-68.pk output pattern test
FAIL: poke.map/maps-uint-write-69.pk output pattern test
FAIL: poke.map/maps-uint-write-70.pk output pattern test
FAIL: poke.map/maps-uint-write-71.pk output pattern test
FAIL: poke.map/maps-uint-write-72.pk output pattern test
FAIL: poke.map/maps-uint-write-73.pk output pattern test
FAIL: poke.map/maps-uint-write-74.pk output pattern test

Example of failure:

FAIL: poke.map/maps-uint-17.pk output pattern test
Output was:
0089674523

Should match:
1589674523