Skip Menu |

This queue is for tickets about the YAML-Tiny CPAN distribution.

Report information
The Basics
Id: 124399
Status: open
Priority: 0/
Queue: YAML-Tiny

People
Owner: Nobody in particular
Requestors: ppisar [...] redhat.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in:
  • 1.70
  • 1.73
Fixed in: (no value)



Subject: t/10_read.t: Failed test 'Got expected error' with Encode 2.95
After upgrading Encode from 2.94 to 2.95 a tests fails: t/01_compile.t ......... ok # Failed test 'Got expected error' # at t/10_read.t line 81. # 'Error reading from file 't/data/utf_16_le_bom.yml': Malformed UTF-8 character: \xff (overflows) in subroutine entry # at t/10_read.t line 79. # ' # doesn't match '(?^:utf_16_le_bom\.yml.*does not map to Unicode)' # Looks like you failed 1 test of 3. # Failed test 'utf_16_le_bom.yml' # at t/10_read.t line 82. # Looks like you failed 1 test of 6. t/10_read.t ............ Dubious, test returned 1 (wstat 256, 0x100) Failed 1/6 subtests This happens with YAML-Tiny-1.70 as well as with current git master HEAD.
From: paul [...] city-fan.org
On Mon Feb 12 05:01:04 2018, ppisar wrote: Show quoted text
> After upgrading Encode from 2.94 to 2.95 a tests fails: > > t/01_compile.t ......... ok > # Failed test 'Got expected error' > # at t/10_read.t line 81. > # 'Error reading from file > 't/data/utf_16_le_bom.yml': Malformed UTF-8 character: \xff > (overflows) in subroutine entry > # at t/10_read.t line 79. > # ' > # doesn't match '(?^:utf_16_le_bom\.yml.*does not map to > Unicode)' > # Looks like you failed 1 test of 3. > # Failed test 'utf_16_le_bom.yml' > # at t/10_read.t line 82. > # Looks like you failed 1 test of 6. > t/10_read.t ............ > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/6 subtests > > This happens with YAML-Tiny-1.70 as well as with current git master > HEAD.
This also affects CPAN-Meta-YAML, which is a derivative of YAML-Tiny.
On Mon Feb 12 05:01:04 2018, ppisar wrote: Show quoted text
> After upgrading Encode from 2.94 to 2.95 a tests fails: > > t/01_compile.t ......... ok > # Failed test 'Got expected error' > # at t/10_read.t line 81. > # 'Error reading from file > 't/data/utf_16_le_bom.yml': Malformed UTF-8 character: \xff > (overflows) in subroutine entry > # at t/10_read.t line 79. > # ' > # doesn't match '(?^:utf_16_le_bom\.yml.*does not map to > Unicode)' > # Looks like you failed 1 test of 3. > # Failed test 'utf_16_le_bom.yml' > # at t/10_read.t line 82. > # Looks like you failed 1 test of 6. > t/10_read.t ............ > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/6 subtests > > This happens with YAML-Tiny-1.70 as well as with current git master > HEAD.
Please try with the recently released Encode 2.96. That version has been merged into Perl 5 blead. Blead is not experiencing any failures in CPAN-Meta-YAML and YAML-Tiny passes all its tests and successfully installs against blead. ##### $ ./bin/perl -v | head -2 | tail -1 This is perl 5, version 27, subversion 9 (v5.27.9 (v5.27.8-253-g141513f)) built for x86_64-linux $ ./bin/cpanm YAML::Tiny --> Working on YAML::Tiny Fetching http://www.cpan.org/authors/id/E/ET/ETHER/YAML-Tiny-1.70.tar.gz ... OK Configuring YAML-Tiny-1.70 ... OK Building and testing YAML-Tiny-1.70 ... OK Successfully installed YAML-Tiny-1.70 1 distribution installed $ ./bin/perl -Ilib -MEncode -MYAML::Tiny -E 'say join(q<|> => $Encode::VERSION, $YAML::Tiny::VERSION)' 2.96|1.70 ##### Thank you very much. Jim Keenan
Subject: Re: [rt.cpan.org #124399] t/10_read.t: Failed test 'Got expected error' with Encode 2.95
Date: Tue, 13 Feb 2018 16:54:18 +0100
To: James E Keenan via RT <bug-YAML-Tiny [...] rt.cpan.org>
From: Petr Pisar <ppisar [...] redhat.com>
On Tue, Feb 13, 2018 at 10:29:41AM -0500, James E Keenan via RT wrote: Show quoted text
> Please try with the recently released Encode 2.96. >
2.96 changes only $VERSION values. I've just tried it with Encode 2.96 and it still fails for me. Show quoted text
> That version has been merged into Perl 5 blead. Blead is not experiencing > any failures in CPAN-Meta-YAML and YAML-Tiny passes all its tests and > successfully installs against blead. >
Interesting. I use Perl 5.26.1. I think Encode 2.95 started to use some new Perl features and it's possible that they are not available on 5.26.1 and that results into a different code path and different error message. <http://matrix.cpantesters.org/?dist=YAML-Tiny+1.70> shows failures on Perl < 5.27.0 only. -- Petr
On 2018-02-13 07:58:24, ppisar wrote: Show quoted text
> Interesting. I use Perl 5.26.1. I think Encode 2.95 started to use > some new > Perl features and it's possible that they are not available on 5.26.1 > and that > results into a different code path and different error message. > <http://matrix.cpantesters.org/?dist=YAML-Tiny+1.70> shows failures on > Perl > < 5.27.0 only.
I can confirm the test failures with Encode 2.96 on perl 5.26.1; Encode 2.94 works. I've added a note to https://github.com/dankogai/p5-encode/pull/128 where Karl and Dan can see it.
From: ppisar [...] redhat.com
Dne Út 13.úno.2018 14:48:08, ETHER napsal(a): Show quoted text
> On 2018-02-13 07:58:24, ppisar wrote: >
> > Interesting. I use Perl 5.26.1. I think Encode 2.95 started to use > > some new > > Perl features and it's possible that they are not available on 5.26.1 > > and that > > results into a different code path and different error message. > > <http://matrix.cpantesters.org/?dist=YAML-Tiny+1.70> shows failures > > on > > Perl > > < 5.27.0 only.
> > I can confirm the test failures with Encode 2.96 on perl 5.26.1; > Encode 2.94 works. > > I've added a note to https://github.com/dankogai/p5-encode/pull/128 > where Karl and Dan can see it.
Encode was corrected in cfaedb2beda37cbc3575ee818c3c83ea87673c32 commit that restores the old warning message on Perl 5.26.