Bug 1375239 - perl-Pegex-0.61-1.fc26 FTBFS: Failed test 'Whitespace Tokens (bootstrap compile)'
Summary: perl-Pegex-0.61-1.fc26 FTBFS: Failed test 'Whitespace Tokens (bootstrap compi...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Pegex
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gerd Pokorra
QA Contact: Fedora Extras Quality Assurance
URL: http://koji.fedoraproject.org/koji/ta...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-12 14:13 UTC by Petr Pisar
Modified: 2017-03-07 10:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-01 19:01:02 UTC
Type: Bug


Attachments (Terms of Use)

Description Petr Pisar 2016-09-12 14:13:34 UTC
perl-Pegex-0.61-1.fc26 fails to build in F26 because tests fail:

t/sample.t ....................... ok
#   Failed test 'Whitespace Tokens (bootstrap compile)'
#   at /usr/share/perl5/vendor_perl/TestML/Runtime.pm line 99.
# --- want
# +++ got
# @@ -1,10 +1,10 @@
#  a:
#    .all:
# -  - .ref: _
# -  - +min: 1
# -    .ref: b
# -  - .ref: __
# -  - .ref: c
# -  - .ref: _
# +    - .ref: _
# +    - +min: 1
# +      .ref: b
# +    - .ref: __
# +    - .ref: c
# +    - .ref: _
#  b:
#    .rgx: <_>cat<__>dog<_>
[...]
Test Summary Report
-------------------
t/testml-compiler-checks.t     (Wstat: 10752 Tests: 74 Failed: 42)
  Failed tests:  2-3, 7-11, 15, 20-31, 35, 39-40, 44-48
                52, 57-68, 72
  Non-zero exit status: 42
t/testml-tree-pegex.t          (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/testml-tree.t                (Wstat: 6144 Tests: 58 Failed: 24)
  Failed tests:  29-30, 32-38, 41-55
  Non-zero exit status: 24
Files=18, Tests=264,  4 wallclock secs ( 0.09 usr  0.03 sys +  2.80 cusr  0.26 csys =  3.18 CPU)
Result: FAIL

This is caused by upgrading perl-YAML-LibYAML from 0.63-1.fc25 to 0.71-1.fc26.

Comment 1 Petr Pisar 2016-09-12 14:40:26 UTC
Paul, where did you get the YAML-LibYAML-0.71 release? I can see it on rurban's gihub fork and CPAN author's listing, but the CPAN search <http://search.cpan.org/dist/YAML-LibYAML/> does not index it. Is that an authorized release?

Comment 2 Paul Howarth 2016-09-12 16:14:13 UTC
It showed up on MetaCPAN last week and I appear to have misread the authorized information. Looks like I'll need to bump epoch and revert to 0.63.

Comment 3 Gerd Pokorra 2016-09-15 03:28:11 UTC
As a workaraund I removed the three tests that fails in build:

https://koji.fedoraproject.org/koji/taskinfo?taskID=15632436

If I use YAML-LibYAML-0.71 on Fedora 24 then I can reproduce the error there.

Comment 4 Gerd Pokorra 2016-09-15 03:48:02 UTC
In the meantime there is YAML-LibYAML-0.73 from rurban. It causes the same errors in the Pegex tests.

Comment 5 Reini Urban 2016-09-15 09:39:21 UTC
Please see https://github.com/rurban/yaml-libyaml-pm/issues/1 which answers your questions.

My CPAN uploads are entirely unauthorized. Please remove them from Fedora.

But they should be.
The Pegex tests are broken, due to the broken interpretation of the YAML specs, which caused the problems with the various perl YAML libraries over the years. See the links.
So in the end Pegex and YAML have to change it's tests to liberate it's whitespace rules, amongst other bugs and inconsistencies.

But this will need a while. I started fixing it in March 2016, and got no feedback so far. Only the cperl toolchain is fixed, but this is a perl5 fork nobody is distributing. And the upstream maintainers are silent.

Comment 6 Fedora End Of Life 2017-02-28 10:14:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 7 Gerd Pokorra 2017-03-01 19:01:02 UTC
It seems that there is no problem any more. A scratch build on f26 completed successful, so I will close this ticket.

https://koji.fedoraproject.org/koji/taskinfo?taskID=18108569

Comment 8 Paul Howarth 2017-03-07 10:53:13 UTC
As there doesn't seem to be any prospect of a new authorized release of YAML-LibYAML any time soon, I've now reverted to 0.63 in F-26 (though it will have to wait for the end of the alpha freeze to appear) and Rawhide.


Note You need to log in before you can comment on or make changes to this bug.