On 20/05/12 04:10, Jonathan Nieder wrote:
Philip Ashmore wrote:
.tf1: pthread_create failed: Resource temporarily unavailable
tf1: pthread_create failed: Resource temporarily unavailable
That's EAGAIN, which usually would mean some resource limit has been
hit (or an out-of-memory condition).
Author: sthibault
Date: 2012-05-20 10:50:59 + (Sun, 20 May 2012)
New Revision: 5252
Modified:
glibc-package/trunk/debian/changelog
glibc-package/trunk/debian/control
glibc-package/trunk/debian/control.in/libc
glibc-package/trunk/debian/control.in/main
Log:
control/{main,libc}:
Author: sthibault
Date: 2012-05-20 16:20:32 + (Sun, 20 May 2012)
New Revision: 5253
Modified:
glibc-package/trunk/debian/changelog
Log:
Fix patch name typo
Modified: glibc-package/trunk/debian/changelog
===
---
Author: sthibault
Date: 2012-05-20 16:30:56 + (Sun, 20 May 2012)
New Revision: 5254
Modified:
glibc-package/trunk/debian/changelog
Log:
fix patch name typo
Modified: glibc-package/trunk/debian/changelog
===
---
Processing commands for cont...@bugs.debian.org:
unarchive 629862
Bug #629862 {Done: Aurelien Jarno aure...@debian.org} [eglibc] FTBFS:
tst-writev fails on amd64 due to changes in kernels = 2.6.37
Unarchived Bug 629862
reopen 629862 =
Bug #629862 {Done: Aurelien Jarno aure...@debian.org}
Processing commands for cont...@bugs.debian.org:
Version: 2.13-6
Unknown command or malformed arguments to command.
notfound 629862 eglibc/2.13-32
Bug #629862 [eglibc] FTBFS: tst-writev fails on amd64 due to changes in kernels
= 2.6.37
No longer marked as found in versions eglibc/2.13-32.
Your message dated Sun, 20 May 2012 14:03:39 -0500
with message-id 20120520190339.GG3000@burratino
and subject line Re: Processed: FTBFS: tst-writev fails on amd64 due to changes
in kernels = 2.6.37
has caused the Debian Bug report #673596,
regarding libc6: FTBFS on wheezy/sid amd64 (test suite
Processing commands for cont...@bugs.debian.org:
# sigh, I can't spell.
found 673596 eglibc/2.13-32
Bug #673596 {Done: Jonathan Nieder jrnie...@gmail.com} [libc6] libc6: FTBFS
on wheezy/sid amd64 (test suite failures)
Marked as found in versions eglibc/2.13-32; no longer marked as found in
Your message dated Sun, 20 May 2012 14:12:26 -0500
with message-id 20120520191226.GI3000@burratino
and subject line Re: Processed: FTBFS: tst-writev fails on amd64 due to changes
in kernels = 2.6.37
has caused the Debian Bug report #629862,
regarding FTBFS: tst-writev fails on amd64 due to
tag 673596 + unreproducible
thanks
On Sun, May 20, 2012 at 04:01:10AM +0100, Philip Ashmore wrote:
On 20/05/12 03:02, Jonathan Nieder wrote:
Hi Philip,
Philip Ashmore wrote:
annexc.out, Error 1 (ignored)
tst-eintr1.out, Error 1
tst-writev.out, Error 1
***
Encountered
Processing commands for cont...@bugs.debian.org:
tag 673596 + unreproducible
Bug #673596 [libc6] libc6: FTBFS on wheezy/sid amd64 (test suite failures)
Added tag(s) unreproducible.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
673596:
Author: sthibault
Date: 2012-05-20 21:04:11 + (Sun, 20 May 2012)
New Revision: 5255
Added:
glibc-package/trunk/debian/patches/hurd-i386/submitted-sendto.diff
Modified:
glibc-package/trunk/debian/changelog
glibc-package/trunk/debian/patches/series
Log:
Processing commands for cont...@bugs.debian.org:
reassign 673711 libc0.1
Bug #673711 [kfreebsd-image-9.0-1-amd64] kfreebsd-9: pthread_cond_timedwait
returns immediately with ETIMEDOUT
Bug reassigned from package 'kfreebsd-image-9.0-1-amd64' to 'libc0.1'.
No longer marked as found in versions
Hi
On 21/05/2012 01:21, Steven Chamberlain wrote:
I find it interesting that this bug led to those glibc errors (double
free or corruption) in #673681 instead of a hang or simple test failure.
Actually this bug does not cause the corruption in #673681: a race
condition in the unit tests is the
14 matches
Mail list logo
