This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: aarch64: buildbot failure since fe05e1cb



On 15/11/2017 12:54, Siddhesh Poyarekar wrote:
> On Wednesday 15 November 2017 08:18 PM, Adhemerval Zanella wrote:
>>> [1]
>>> http://glibc-buildbot.reserved-bit.com/builders/glibc-aarch64-linux/builds/760
>>>
>>
>> It was reported failures in all architectures in fact and I changed back
>> to old semantic of not using WNOHANG on aa95a2414e4. Is it still failing?
> 
> Yes, all checks since this one have been failing.
> 
> Siddhesh
> 

It is really unexpected because the semantic of spawni should be equal 
to the one before fe05e1cb. I am trying to reproduce it on my aarch64 
environment (4.4.0-62-generic), but without much success.  Also I am 
not seeing this issue on powerpc64le (which Tulio raised an issue with
fe05e1cb), neither on sparc64 (which I also observed intermittent 
failures). I am also checking on powerpc and arm.

In fact I did see an issue on aarch64, but it is unrelated to the
spawni itself. I am running test-spawn2 in a continuous loop on a
container system and after 26556 I got a 'Cannot fork' message
(most likely due a pid limit from container).


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]