Bug#648623: perl: test failures on hurd-i386

2011-11-27 Thread Dominic Hargreaves
On Sat, Nov 26, 2011 at 11:39:08AM +, Dominic Hargreaves wrote:
 On Sun, Nov 20, 2011 at 10:20:22AM +0200, Niko Tyni wrote:
  On Sun, Nov 13, 2011 at 04:51:29PM +0100, Samuel Thibault wrote:
   Package: perl
   Version: 5.14.2-2
   Severity: normal
   User: debian-h...@lists.debian.org
   Usertags: hurd
  
   A few tests fail on hurd-i386:
   
   Failed 9 tests out of 2029, 99.56% okay.
   ../cpan/Sys-Syslog/t/syslog.t
   ../cpan/Time-HiRes/t/HiRes.t
   ../cpan/autodie/t/recv.t
   ../dist/IO/t/io_pipe.t
   ../dist/threads/t/libc.t
   ../dist/threads/t/stack.t
   ../ext/Socket/t/socketpair.t
   io/pipe.t
   op/sigdispatch.t
   
   Could you mark them as TODO on GNU/Hurd?
  
  Has anybody looked at the issues behind these failures?
  
  I'd like to have a separate bug for each one, whether in hurd or perl,
  so that we could at least refer to them in the Debian patch that marks
  the tests as TODO.
  
  However, instead of patching the tests, I think I'd actually prefer just
  making debian/rules ignore test failures on GNU/Hurd so that the failures
  would stay visible in the build log. Possibly this should be accompanied
  by an RC bug on hurd so that the issues have to be resolved one way
  or another if it becomes a release architecture.
  
  Ignoring errors obviously has the downside of not catching any
  regressions automatically. I suppose the hurd folks would need to assume
  responsibility for that.
  
  I don't feel very strongly about this; please let me know what you think.
 
 I was about to implement this, but then I realised that ignoring the result
 of the whole test suite runs a real risk of installing a perl which is
 completely (or significantly) broken because of some other external change,
 so I think I'm swaying back towards the idea of patching out the failing
 tests instead.
 
 Definitely agree we should have bugs for each of the known failures.

Bugs now created, and I'm almost done with the patches TODOing/SKIPing
tests as appropriate. If there are no objections I'll push this
later today or during the week.

Cheers,
Dominic.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#648623: perl: test failures on hurd-i386

2011-11-26 Thread Dominic Hargreaves
On Sun, Nov 20, 2011 at 10:20:22AM +0200, Niko Tyni wrote:
 On Sun, Nov 13, 2011 at 04:51:29PM +0100, Samuel Thibault wrote:
  Package: perl
  Version: 5.14.2-2
  Severity: normal
  User: debian-h...@lists.debian.org
  Usertags: hurd
 
  A few tests fail on hurd-i386:
  
  Failed 9 tests out of 2029, 99.56% okay.
  ../cpan/Sys-Syslog/t/syslog.t
  ../cpan/Time-HiRes/t/HiRes.t
  ../cpan/autodie/t/recv.t
  ../dist/IO/t/io_pipe.t
  ../dist/threads/t/libc.t
  ../dist/threads/t/stack.t
  ../ext/Socket/t/socketpair.t
  io/pipe.t
  op/sigdispatch.t
  
  Could you mark them as TODO on GNU/Hurd?
 
 Has anybody looked at the issues behind these failures?
 
 I'd like to have a separate bug for each one, whether in hurd or perl,
 so that we could at least refer to them in the Debian patch that marks
 the tests as TODO.
 
 However, instead of patching the tests, I think I'd actually prefer just
 making debian/rules ignore test failures on GNU/Hurd so that the failures
 would stay visible in the build log. Possibly this should be accompanied
 by an RC bug on hurd so that the issues have to be resolved one way
 or another if it becomes a release architecture.
 
 Ignoring errors obviously has the downside of not catching any
 regressions automatically. I suppose the hurd folks would need to assume
 responsibility for that.
 
 I don't feel very strongly about this; please let me know what you think.

I was about to implement this, but then I realised that ignoring the result
of the whole test suite runs a real risk of installing a perl which is
completely (or significantly) broken because of some other external change,
so I think I'm swaying back towards the idea of patching out the failing
tests instead.

Definitely agree we should have bugs for each of the known failures.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#648623: perl: test failures on hurd-i386

2011-11-22 Thread Dominic Hargreaves
On Sun, Nov 20, 2011 at 10:20:22AM +0200, Niko Tyni wrote:
 On Sun, Nov 13, 2011 at 04:51:29PM +0100, Samuel Thibault wrote:
  Package: perl
  Version: 5.14.2-2
  Severity: normal
  User: debian-h...@lists.debian.org
  Usertags: hurd
 
  A few tests fail on hurd-i386:
  
  Failed 9 tests out of 2029, 99.56% okay.
  ../cpan/Sys-Syslog/t/syslog.t
  ../cpan/Time-HiRes/t/HiRes.t
  ../cpan/autodie/t/recv.t
  ../dist/IO/t/io_pipe.t
  ../dist/threads/t/libc.t
  ../dist/threads/t/stack.t
  ../ext/Socket/t/socketpair.t
  io/pipe.t
  op/sigdispatch.t
  
  Could you mark them as TODO on GNU/Hurd?
 
 Has anybody looked at the issues behind these failures?
 
 I'd like to have a separate bug for each one, whether in hurd or perl,
 so that we could at least refer to them in the Debian patch that marks
 the tests as TODO.

I agree.

 However, instead of patching the tests, I think I'd actually prefer just
 making debian/rules ignore test failures on GNU/Hurd so that the failures
 would stay visible in the build log. Possibly this should be accompanied
 by an RC bug on hurd so that the issues have to be resolved one way
 or another if it becomes a release architecture.

The effect of TODO in t/test.pl it to run the tests but not make them
fatal, I believe, so I don't think this holds?

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#648623: perl: test failures on hurd-i386

2011-11-22 Thread Niko Tyni
On Tue, Nov 22, 2011 at 11:50:10PM +, Dominic Hargreaves wrote:
 On Sun, Nov 20, 2011 at 10:20:22AM +0200, Niko Tyni wrote:

  However, instead of patching the tests, I think I'd actually prefer just
  making debian/rules ignore test failures on GNU/Hurd so that the failures
  would stay visible in the build log. Possibly this should be accompanied
  by an RC bug on hurd so that the issues have to be resolved one way
  or another if it becomes a release architecture.
 
 The effect of TODO in t/test.pl it to run the tests but not make them
 fatal, I believe, so I don't think this holds?

Those TODO failures are then visible only in verbose mode. Consider:

  % ./perl t/TEST  io/perlio_leaks.t 
  t/io/perlio_leaksok
  All tests successful.
  u=0.00  s=0.00  cu=0.00  cs=0.00  scripts=1  tests=12

vs.

  % ./perl t/TEST -v io/perlio_leaks.t
  t/io/perlio_leaksok 1 - :unix
  not ok 2 - :unix # TODO [perl #56644] PerlIO resource leaks on open() and 
then :pop in :unix and :stdio
  # Failed at io/perlio_leaks.t line 30
  #  got 4
  # expected 3
  not ok 3 - :unix # TODO [perl #56644] PerlIO resource leaks on open() and 
then :pop in :unix and :stdio
  # Failed at io/perlio_leaks.t line 30
  #  got 5
  # expected 3
  ok 4 - :stdio
  not ok 5 - :stdio # TODO [perl #56644] PerlIO resource leaks on open() and 
then :pop in :unix and :stdio
  # Failed at io/perlio_leaks.t line 30
  #  got 7
  # expected 6
  not ok 6 - :stdio # TODO [perl #56644] PerlIO resource leaks on open() and 
then :pop in :unix and :stdio
  # Failed at io/perlio_leaks.t line 30
  #  got 8
  # expected 6
  ok 7 - :perlio
  ok 8 - :perlio
  ok 9 - :perlio
  ok 10 - :crlf
  ok 11 - :crlf
  ok 12 - :crlf
  1..12
  ok
  All tests successful.
  u=0.00  s=0.00  cu=0.01  cs=0.00  scripts=1  tests=12

-- 
Niko Tyni   nt...@debian.org



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#648623: perl: test failures on hurd-i386

2011-11-20 Thread Niko Tyni
On Sun, Nov 13, 2011 at 04:51:29PM +0100, Samuel Thibault wrote:
 Package: perl
 Version: 5.14.2-2
 Severity: normal
 User: debian-h...@lists.debian.org
 Usertags: hurd

 A few tests fail on hurd-i386:
 
 Failed 9 tests out of 2029, 99.56% okay.
 ../cpan/Sys-Syslog/t/syslog.t
 ../cpan/Time-HiRes/t/HiRes.t
 ../cpan/autodie/t/recv.t
 ../dist/IO/t/io_pipe.t
 ../dist/threads/t/libc.t
 ../dist/threads/t/stack.t
 ../ext/Socket/t/socketpair.t
 io/pipe.t
 op/sigdispatch.t
 
 Could you mark them as TODO on GNU/Hurd?

Has anybody looked at the issues behind these failures?

I'd like to have a separate bug for each one, whether in hurd or perl,
so that we could at least refer to them in the Debian patch that marks
the tests as TODO.

However, instead of patching the tests, I think I'd actually prefer just
making debian/rules ignore test failures on GNU/Hurd so that the failures
would stay visible in the build log. Possibly this should be accompanied
by an RC bug on hurd so that the issues have to be resolved one way
or another if it becomes a release architecture.

Ignoring errors obviously has the downside of not catching any
regressions automatically. I suppose the hurd folks would need to assume
responsibility for that.

I don't feel very strongly about this; please let me know what you think.
-- 
Niko Tyni   nt...@debian.org



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#648623: perl: test failures on hurd-i386

2011-11-13 Thread Samuel Thibault
Package: perl
Version: 5.14.2-2
Severity: normal
User: debian-h...@lists.debian.org
Usertags: hurd

Hello,

A few tests fail on hurd-i386:

Failed 9 tests out of 2029, 99.56% okay.
../cpan/Sys-Syslog/t/syslog.t
../cpan/Time-HiRes/t/HiRes.t
../cpan/autodie/t/recv.t
../dist/IO/t/io_pipe.t
../dist/threads/t/libc.t
../dist/threads/t/stack.t
../ext/Socket/t/socketpair.t
io/pipe.t
op/sigdispatch.t

Could you mark them as TODO on GNU/Hurd?

Thanks,
Samuel

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages perl depends on:
ii  libbz2-1.01.0.5-7 
ii  libc6 2.13-21 
ii  libdb5.1  5.1.25-11   
ii  libgdbm3  1.8.3-10
ii  perl-base 5.12.4-6
ii  perl-modules  5.12.4-6
ii  zlib1g1:1.2.3.4.dfsg-3

Versions of packages perl recommends:
ii  netbase  4.47

Versions of packages perl suggests:
ii  libterm-readline-gnu-perl | libterm-readline-perl-perl  none  
ii  make3.81-8.1
ii  perl-doc5.12.4-6

-- no debconf information

-- 
Samuel Thibault samuel.thiba...@fnac.net
*** s has joined channel #ens-mim
N re 
s pfff 
s mare de la pfp. 
s pas commencer et j'en ai deja marre. 
s bon ct juste un cou de gueule ++ 
*** s has left channel #ens-mim (s)
 -+- #ens-mim et la peufeupeu -+-



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#648623: perl: test failures on hurd-i386

2011-11-13 Thread Dominic Hargreaves
tags 648623 +confirmed
thanks

On Sun, Nov 13, 2011 at 04:51:29PM +0100, Samuel Thibault wrote:
 A few tests fail on hurd-i386:
 
 Failed 9 tests out of 2029, 99.56% okay.
 ../cpan/Sys-Syslog/t/syslog.t
 ../cpan/Time-HiRes/t/HiRes.t
 ../cpan/autodie/t/recv.t
 ../dist/IO/t/io_pipe.t
 ../dist/threads/t/libc.t
 ../dist/threads/t/stack.t
 ../ext/Socket/t/socketpair.t
 io/pipe.t
 op/sigdispatch.t
 
 Could you mark them as TODO on GNU/Hurd?

Yup, will do this after the initial 5.14 upload to unstable.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org