[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: race condition destroying condition variables
|
From: |
Svante Signell |
|
Subject: |
Re: race condition destroying condition variables |
|
Date: |
Fri, 22 Dec 2017 00:34:55 +0100 |
On Fri, 2017-12-22 at 00:22 +0100, Samuel Thibault wrote:
>
> >
> > The testsuite for glibc is known to be broken. Just
> > export DEB_BUILD_OPTIONS=nocheck before building
> > with dpkg-buildpackage -b ...
>
> Broken tests are marked as such, there aren't so many marked as such.
>
> Using nocheck is a way to avoid the issue indeed.
>
> The build boxes have 3GB memory and 4GB swap, and do pass the
> testsuite
> fine (minus the marked tests)
Well, I've never managed to build glibc with tests enabled. And it
takes a much longer time to build. But of course YMWV.
- race condition destroying condition variables, Brent W. Baccala, 2017/12/19
- Re: race condition destroying condition variables, Samuel Thibault, 2017/12/19
- Re: race condition destroying condition variables, Richard Braun, 2017/12/19
- Re: race condition destroying condition variables, Brent W. Baccala, 2017/12/19
- Re: race condition destroying condition variables, Brent W. Baccala, 2017/12/21
- Re: race condition destroying condition variables, Svante Signell, 2017/12/21
- Re: race condition destroying condition variables, Samuel Thibault, 2017/12/21
- Re: race condition destroying condition variables,
Svante Signell <=
- Re: race condition destroying condition variables, Brent W. Baccala, 2017/12/26
- Re: race condition destroying condition variables, Samuel Thibault, 2017/12/27
- Re: race condition destroying condition variables, Brent W. Baccala, 2017/12/27
- Re: race condition destroying condition variables, Samuel Thibault, 2017/12/27