# New Ticket Created by James E Keenan # Please include the string: [perl #134217] # in the subject line of all future correspondence about this issue. # <URL: https://rt.perl.org/Ticket/Display.html?id=134217 > In https://rt.perl.org/Ticket/Display.html?id=134215, Andreas reported test failures in a number of files. Most of these turned out to be porting or corelist-related tests and have been fixed as of commit 9965e4913ae5c95c055633458dda05e8244efd1a. However, there are still failures in dist/Devel-PPPort/t/uv.t. ##### $ cd t;./perl harness ../dist/Devel-PPPort/t/uv.t; cd - # Test 25 got: "1" (t/uv.t at line 99) # Expected: "-1" ../dist/Devel-PPPort/t/uv.t .. 1/52 # Test 29 got: "0" (t/uv.t at line 164) # Expected: "-1" (returned length utf8_to_uvchr_buf(""); warnings enabled) # Test 31 got: "0" (t/uv.t at line 172) # Expected: "65533" (returned value utf8_to_uvchr_buf(""); warnings disabled) # Test 34 got: "1" (t/uv.t at line 164 fail #2) # Expected: "-1" (returned length utf8_to_uvchr_buf("\xc4\xc5"); warnings enabled) # Test 39 got: "1" (t/uv.t at line 164 fail #3) # Expected: "-1" (returned length utf8_to_uvchr_buf("\xc4"); warnings enabled) # Test 44 got: "2" (t/uv.t at line 164 fail #4) # Expected: "-1" (returned length utf8_to_uvchr_buf("\xc0\x81"); warnings enabled) # Test 49 got: "13" (t/uv.t at line 164 fail #5) # Expected: "-1" (returned length utf8_to_uvchr_buf("\xff\x80\x90\x90\x90\xbf\xbf\xbf\xbf\xbf\xbf\xbf\xbf"); warnings enabled) ../dist/Devel-PPPort/t/uv.t .. Failed 7/52 subtests Test Summary Report ------------------- ../dist/Devel-PPPort/t/uv.t (Wstat: 0 Tests: 52 Failed: 7) Failed tests: 25, 29, 31, 34, 39, 44, 49 Files=1, Tests=52, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.03 cusr 0.01 csys = 0.05 CPU) Result: FAIL ##### Bisection pointed to: ##### 70bcccc1440e5a391d6d656659da06ccc887296c is the first bad commit commit 70bcccc1440e5a391d6d656659da06ccc887296c Author: Karen Etheridge <ether@cpan.org> Date: Thu Jun 20 13:22:45 2019 -0700 bump version to 5.31.2 ##### ... but I'm not sure that's accurate as I can't understand why a commit of version bumps would trigger these PPPort failures. But, in any event, there have been extensive changes in Devel-PPPort since 5.31.0. Thank you very much. Jim KeenanThread Previous