From @eserte

This is a bug report for perl from slaven@​rezic.de,
generated with the help of perlbug 1.39 running under perl 5.14.0.

With v5.13.11-423-g90803c3 I see some new failures which did not
appear in v5.13.11-389-g9b02939. Most prominent are​:

Mojolicious-1.15 <FAIL> vs. <PASS>
CHI-0.44 <FAIL> vs. <PASS>
Text-CSV_XS-0.81 <FAIL> vs. <PASS>

ANDK did a bisect with CHI and Text-CSV_XS and found out that commit
efc5c7c caused the breakage.

Regards,
  Slaven

Flags​:
  category=core
  severity=high

Site configuration information for perl 5.14.0​:

Configured by cpansand at Tue Apr 12 23​:20​:10 CEST 2011.

Summary of my perl5 (revision 5 version 14 subversion 0) configuration​:
  Commit id​: 90803c3
  Platform​:
  osname=freebsd, osvers=8.0-release, archname=i386-freebsd
  uname='freebsd biokovo.herceg.de 8.0-release freebsd 8.0-release #0​: sat nov 21 15​:48​:17 utc 2009 root@​almeida.cse.buffalo.edu​:usrobjusrsrcsysgeneric i386 '
  config_args='-ds -e -Uversiononly -Dinstallusrbinperl=n -Dusedevel -Dprefix=/home/cpansand/var/ctps/5140RC0_3/install/perl-v5.13.11-423-g90803c3'
  hint=recommended, useposix=true, d_sigaction=define
  useithreads=undef, usemultiplicity=undef
  useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
  use64bitint=undef, use64bitall=undef, uselongdouble=undef
  usemymalloc=n, bincompat5005=undef
  Compiler​:
  cc='cc', ccflags ='-DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include',
  optimize='-O',
  cppflags='-DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include'
  ccversion='', gccversion='4.2.1 20070719 [FreeBSD]', gccosandvers=''
  intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
  d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
  ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
  alignbytes=4, prototype=define
  Linker and Libraries​:
  ld='cc', ldflags ='-Wl,-E -fstack-protector -L/usr/local/lib'
  libpth=/usr/lib /usr/local/lib
  libs=-lgdbm -lm -lcrypt -lutil -lc
  perllibs=-lm -lcrypt -lutil -lc
  libc=, so=so, useshrplib=false, libperl=libperl.a
  gnulibc_version=''
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
  cccdlflags='-DPIC -fPIC', lddlflags='-shared -L/usr/local/lib -fstack-protector'

Locally applied patches​:
  RC0

@​INC for perl 5.14.0​:
  /home/cpansand/var/ctps/5140RC0_3/install/perl-v5.13.11-423-g90803c3/lib/site_perl/5.14.0/i386-freebsd
  /home/cpansand/var/ctps/5140RC0_3/install/perl-v5.13.11-423-g90803c3/lib/site_perl/5.14.0
  /home/cpansand/var/ctps/5140RC0_3/install/perl-v5.13.11-423-g90803c3/lib/5.14.0/i386-freebsd
  /home/cpansand/var/ctps/5140RC0_3/install/perl-v5.13.11-423-g90803c3/lib/5.14.0
  .

Environment for perl 5.14.0​:
  HOME=/home/e/eserte
  LANG (unset)
  LANGUAGE (unset)
  LC_ALL=de_DE.ISO8859-1
  LC_CTYPE=de_DE.ISO8859-1
  LD_LIBRARY_PATH (unset)
  LOGDIR (unset)
  PATH=/usr/local/bin​:/usr/bin​:/bin​:/usr/gnu/bin​:/usr/TeX/bin​:/usr/local/sbin​:/usr/sbin​:/sbin​:/usr/local/pilot/bin​:/home/e/eserte/bin/FreeBSD​:/home/e/eserte/bin/sh​:/home/e/eserte/bin​:/usr/X11R6/bin​:/usr/X11/bin​:/usr/X386/bin​:/usr/games​:/home/e/eserte/devel
  PERLDOC=-MPod​::Perldoc​::ToTextOverstrike
  PERL_BADLANG (unset)
  PERL_HTML_DISPLAY_CLASS=HTML​::Display​::Mozilla
  SHELL=/bin/tcsh

From @andk

Mojolicious-1.15 <FAIL> vs. <PASS>
CHI-0.44 <FAIL> vs. <PASS>
Text-CSV_XS-0.81 <FAIL> vs. <PASS>

ANDK did a bisect with CHI and Text-CSV_XS and found out that commit
efc5c7c caused the breakage.

Confirmed also for KRAIH/Mojolicious-1.15.tar.gz.

Another case is SAKOHT/RMI-0.10.tar.gz​: a test hangs since that change,
so doesn't send FAIL reports.

--
andreas

The RT System itself - Status changed from 'new' to 'open'

From @Tux

On Thu, 14 Apr 2011 05​:46​:50 +0200,
andreas.koenig.7os6VVqR@​franz.ak.mind.de (Andreas J. Koenig) wrote​:

Mojolicious-1.15 <FAIL> vs. <PASS>
CHI-0.44 <FAIL> vs. <PASS>
Text-CSV_XS-0.81 <FAIL> vs. <PASS>
  ^^^^^^^^^^^

I didn't notice. Maybe I didn't pay enough attention. Should I do
something? I can change the innards to match the correct behaviour

ANDK did a bisect with CHI and Text-CSV_XS and found out that commit
efc5c7c caused the breakage.

Looks related. And I'm awfully curious to see if this commit does
relate to http​://rt.cpan.org/Public/Bug/Display.html?id=66474 which
I - at least till now - was not able to fix.

--
H.Merijn Brand http​://tux.nl Perl Monger http​://amsterdam.pm.org/
using 5.00307 through 5.12 and porting perl5.13.x on HP-UX 10.20, 11.00,
11.11, 11.23 and 11.31, OpenSuSE 10.1, 11.0 .. 11.3 and AIX 5.2 and 5.3.
http​://mirrors.develooper.com/hpux/ http​://www.test-smoke.org/
http​://qa.perl.org http​://www.goldmark.org/jeff/stupid-disclaimers/

From @eserte

"(Andreas J. Koenig) via RT" <perlbug-followup@​perl.org> writes​:

Mojolicious-1.15 <FAIL> vs. <PASS>
CHI-0.44 <FAIL> vs. <PASS>
Text-CSV_XS-0.81 <FAIL> vs. <PASS>

ANDK did a bisect with CHI and Text-CSV_XS and found out that commit
efc5c7c caused the breakage.

Confirmed also for KRAIH/Mojolicious-1.15.tar.gz.

Another case is SAKOHT/RMI-0.10.tar.gz​: a test hangs since that change,
so doesn't send FAIL reports.

Confirmed on my FreeBSD system with v5.13.11-423-g90803c3. The last
message when running the test suite is​:

module IO/File.pm has already been used locally from path​: /home/cpansand/var/ctps/5140RC0_3/install/perl-v5.13.11-423-g90803c3/lib/5.14.0/i386-freebsd/IO/File.pm at /var/tmp/CPAN-build/RMI-0.10-eZa7Zh/blib/lib/RMI/Node.pm line 630, <GEN0> line 22.
# Looks like you planned 20 tests but ran 18.
# Looks like your test exited with 255 just after 18.

Regards,
  Slaven

--
Slaven Rezic - slaven <at> rezic <dot> de

  tktimex - time recording tool
  http​://sourceforge.net/projects/ptktools/

From @cpansprout

On Wed Apr 13 23​:08​:32 2011, hmbrand wrote​:

On Thu, 14 Apr 2011 05​:46​:50 +0200,
andreas.koenig.7os6VVqR@​franz.ak.mind.de (Andreas J. Koenig) wrote​:

Mojolicious-1.15 <FAIL> vs. <PASS>
CHI-0.44 <FAIL> vs. <PASS>
Text-CSV_XS-0.81 <FAIL> vs. <PASS>
^^^^^^^^^^^

I didn't notice. Maybe I didn't pay enough attention. Should I do
something? I can change the innards to match the correct behaviour

ANDK did a bisect with CHI and Text-CSV_XS and found out that commit
efc5c7c caused the breakage.

Looks related. And I'm awfully curious to see if this commit does
relate to http​://rt.cpan.org/Public/Bug/Display.html?id=66474 which
I - at least till now - was not able to fix.

Sorry to disappoint you. I think I’ve just fixed this with commit 221e5db.

From @Tux

On Thu, 14 Apr 2011 06​:28​:45 -0700, "Father Chrysostomos via RT"
<perlbug-followup@​perl.org> wrote​:

On Wed Apr 13 23​:08​:32 2011, hmbrand wrote​:

On Thu, 14 Apr 2011 05​:46​:50 +0200,
andreas.koenig.7os6VVqR@​franz.ak.mind.de (Andreas J. Koenig) wrote​:

Mojolicious-1.15 <FAIL> vs. <PASS>
CHI-0.44 <FAIL> vs. <PASS>
Text-CSV_XS-0.81 <FAIL> vs. <PASS>
^^^^^^^^^^^

I didn't notice. Maybe I didn't pay enough attention. Should I do
something? I can change the innards to match the correct behaviour

ANDK did a bisect with CHI and Text-CSV_XS and found out that commit
efc5c7c caused the breakage.

Looks related. And I'm awfully curious to see if this commit does
relate to http​://rt.cpan.org/Public/Bug/Display.html?id=66474 which
I - at least till now - was not able to fix.

Sorry to disappoint you. I think I’ve just fixed this with commit 221e5db.

disappoint me? You're kidding :)

All tests successful.
Files=24, Tests=13500, 4 wallclock secs ( 1.94 usr 0.11 sys + 3.27 cusr 0.21 csys = 5.53 CPU)
Result​: PASS

It indeed does not fix RT#66474, maybe that is what you mean could
disappoint me.

Maybe that should be RT'd

--
H.Merijn Brand http​://tux.nl Perl Monger http​://amsterdam.pm.org/
using 5.00307 through 5.12 and porting perl5.13.x on HP-UX 10.20, 11.00,
11.11, 11.23 and 11.31, OpenSuSE 10.1, 11.0 .. 11.3 and AIX 5.2 and 5.3.
http​://mirrors.develooper.com/hpux/ http​://www.test-smoke.org/
http​://qa.perl.org http​://www.goldmark.org/jeff/stupid-disclaimers/

From @cpansprout

I’ve just tested blead with all the affected modules. It seems my fix
worked.

@cpansprout - Status changed from 'open' to 'resolved'