Bug#713035: FTBFS on amd64/ia64 testsuite fails

2013-06-29 Thread Modestas Vainius
Hello,

Ketvirtadienis 27 Birželis 2013 14:37:17 rašė:
 On Thu, Jun 27, 2013 at 08:05:17PM +0200, Aurelien Jarno wrote:
  The problem is that the amd64 and ia64 build daemons which tried to
  build this version of eglibc are all using eatmydata. eatmydata do not
  correctly simulate fsync, msync and fdatasync as cancellation points. It
  should be possible fixing that by calling pthread_testcancel() from
  eatmydata, though I haven't tried that yet.
 
 It seems pretty testsuite-hostile to wrap builds in any LD_PRELOAD, as
 you have no idea if the thing(s) the testsuites might be checking are
 now invalidated by said preload.
 
 Was there actually a sane rationale put forward for this buildd change?
 I can see the argument for wanting the apt/dpkg bits wrapped, but doing
 so for the build itself just seems like asking for trouble, with very
 little potential gain.

Speaking with my maintainer hat on, when I first came upon eatmydata, I 
thought: it will be a huge time saviour for personal and maybe debian buildds. 
My primary idea was to wrap apt/dpkg with eatmydata since they use fsync() and 
friends *really* extensively. Too bad fsync() used to be (still is?) very slow 
on btrfs filesystem.

For exactly this purpose eatmydata script supports symlink mode (see 
eatmydata(1)). Doing:

# ln -s /usr/bin/eatmydata /usr/local/bin/apt-get
# ln -s /usr/bin/eatmydata /usr/local/bin/dpkg

in the buildd environment should be enough to wrap only these tools without 
too much hassle (i.e. sbuild configuration changes).

I'm not sure how I feel about wrapping the whole build. Maybe it's not such a 
bad idea after all if somebody tested that it speeded things up much more 
significantly. However, I just wanted to let you know that a more conservative  
approach is possible.

P.S. I'm aware that upstream released a new upstream release with the fix for 
this bug. However, packaging it might take some time due to significant 
buildsystem changes and other stuff. However, hopefully, I will get it 
eventually done in a few weeks.

-- 
Modestas Vainius mo...@debian.org


signature.asc
Description: This is a digitally signed message part.


Bug#713035: FTBFS on amd64/ia64 testsuite fails

2013-06-27 Thread Aurelien Jarno
On Sat, Jun 22, 2013 at 12:55:56AM +0200, Gianluigi Tiesi wrote:
 Package: libc6
 Version: 2.17-5
 Severity: important
 
 libc6 2.17-6 FTBFS on amd64 and ia64 architectures due to
 some testsuite checks
 
 look at https://buildd.debian.org/status/package.php?p=eglibcsuite=sid
 

The problem is that the amd64 and ia64 build daemons are using eatmydata
to speed-up the build process. It causes some tests to fails, as
eatmydata doesn't simulate the sync functions as cancellation point.

So the problem is not on the eglibc side, and I don't know what we can
do on the package side.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


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



Bug#713035: FTBFS on amd64/ia64 testsuite fails

2013-06-27 Thread Gianluigi Tiesi

On 06/27/13 16:37, Aurelien Jarno wrote:

On Sat, Jun 22, 2013 at 12:55:56AM +0200, Gianluigi Tiesi wrote:

Package: libc6
Version: 2.17-5
Severity: important

libc6 2.17-6 FTBFS on amd64 and ia64 architectures due to
some testsuite checks

look at https://buildd.debian.org/status/package.php?p=eglibcsuite=sid



The problem is that the amd64 and ia64 build daemons are using eatmydata
to speed-up the build process. It causes some tests to fails, as
eatmydata doesn't simulate the sync functions as cancellation point.

So the problem is not on the eglibc side, and I don't know what we can
do on the package side.



the bug may be forwarded to eatmydata package, eglibc will not build 
anymore on that platform


Regards

--
Gianluigi Tiesi sher...@netfarm.it
EDP Project Leader
Netfarm S.r.l. - http://www.netfarm.it/
Free Software: http://oss.netfarm.it/

Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?


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



Bug#713035: FTBFS on amd64/ia64 testsuite fails

2013-06-27 Thread Aurelien Jarno
clone 713035 -1
reassign -1 eatmydata 
retitle -1 eatmydata does not simulate fsync, msync and fdatasync as 
cancellation points
clone 713035 -2
reassign -2 buildd.debian.org
retitle -2 buildds should not use eatmydata until it correctly simulates 
cancellation points
retitle 713035 eglibc: FTBFS when built with eatmydata
severity 713035 normal
thanks

On Sat, Jun 22, 2013 at 12:55:56AM +0200, Gianluigi Tiesi wrote:
 Package: libc6
 Version: 2.17-5
 Severity: important
 
 libc6 2.17-6 FTBFS on amd64 and ia64 architectures due to
 some testsuite checks
 
 look at https://buildd.debian.org/status/package.php?p=eglibcsuite=sid
 

The problem is that the amd64 and ia64 build daemons which tried to
build this version of eglibc are all using eatmydata. eatmydata do not
correctly simulate fsync, msync and fdatasync as cancellation points. It
should be possible fixing that by calling pthread_testcancel() from
eatmydata, though I haven't tried that yet.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


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



Bug#713035: FTBFS on amd64/ia64 testsuite fails

2013-06-27 Thread Adam Conrad
On Thu, Jun 27, 2013 at 08:05:17PM +0200, Aurelien Jarno wrote:
 
 The problem is that the amd64 and ia64 build daemons which tried to
 build this version of eglibc are all using eatmydata. eatmydata do not
 correctly simulate fsync, msync and fdatasync as cancellation points. It
 should be possible fixing that by calling pthread_testcancel() from
 eatmydata, though I haven't tried that yet.

It seems pretty testsuite-hostile to wrap builds in any LD_PRELOAD, as
you have no idea if the thing(s) the testsuites might be checking are
now invalidated by said preload.

Was there actually a sane rationale put forward for this buildd change?
I can see the argument for wanting the apt/dpkg bits wrapped, but doing
so for the build itself just seems like asking for trouble, with very
little potential gain.

... Adam


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



Bug#713035: FTBFS on amd64/ia64 testsuite fails

2013-06-21 Thread Gianluigi Tiesi
Package: libc6
Version: 2.17-5
Severity: important

libc6 2.17-6 FTBFS on amd64 and ia64 architectures due to
some testsuite checks

look at https://buildd.debian.org/status/package.php?p=eglibcsuite=sid

Regards

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

Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6 depends on:
ii  libgcc1  1:4.8.1-3

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.50
ii  glibc-doc  2.17-5
ii  locales2.17-5

-- debconf information excluded


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