https://bugzilla.redhat.com/show_bug.cgi?id=1420326

            Bug ID: 1420326
           Summary: perl-5.24.1-387.fc26 FTBFS: tests fail with zlib ≥
                    1.2.9
           Product: Fedora
           Version: rawhide
         Component: perl
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected]
        Depends On: 1420012, 1419841



perl-5.24.1-387.fc26 fails to build in F26 because tests fail:

Test Summary Report
-------------------
../cpan/Compress-Raw-Zlib/t/02zlib.t                            (Wstat: 1280
Tests: 317 Failed: 5)
  Failed tests:  148, 152, 156, 164-165
  Non-zero exit status: 5
../cpan/IO-Compress/t/cz-03zlib-v1.t                            (Wstat: 1280
Tests: 471 Failed: 5)
  Failed tests:  208, 212, 216, 224-225
  Non-zero exit status: 5
../cpan/IO-Compress/t/cz-06gzsetp.t                             (Wstat: 3840
Tests: 51 Failed: 15)
  Failed tests:  6, 11-13, 19, 23-25, 31, 35-37, 43, 47-48
  Non-zero exit status: 15
Files=2412, Tests=861992, 442 wallclock secs (173.62 usr 10.37 sys + 983.15
cusr 48.74 csys = 1215.88 CPU)
Result: FAIL

This is caused by upgrading zlib from 1.2.8 to 1.2.9. Fixes for bundled
IO-Compress and Compress-Raw-Zlib must be ported.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1419841
[Bug 1419841] perl-Compress-Raw-Zlib-2.071-1.fc26 FTBFS: deflateParams()
tests in t/02zlib.t fail with zlib ≥ 1.2.9
https://bugzilla.redhat.com/show_bug.cgi?id=1420012
[Bug 1420012] perl-IO-Compress-2.070-1.fc26 FTBS: tests fail with zlib ≥
1.2.9
-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
perl-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to