Emilio G. Cota writes:
> On Fri, Jan 11, 2019 at 19:10:07 +, Alex Bennée wrote:
>> So trying to narrow down the remaining failures in the CI system. There
>> is one with a patch in flight (use g_usleep instead of sleep) but there
>> remains two failure modes, both erratic.
>>
>>
On Mon, Jan 14, 2019 at 10:02:06AM -0500, Emilio G. Cota wrote:
> On Fri, Jan 11, 2019 at 19:10:07 +, Alex Bennée wrote:
> > So trying to narrow down the remaining failures in the CI system. There
> > is one with a patch in flight (use g_usleep instead of sleep) but there
> > remains two
On Fri, Jan 11, 2019 at 19:10:07 +, Alex Bennée wrote:
> So trying to narrow down the remaining failures in the CI system. There
> is one with a patch in flight (use g_usleep instead of sleep) but there
> remains two failure modes, both erratic.
>
> tests/qht-par:
>
> I can trigger this on
On Fri, 11 Jan 2019 at 19:10, Alex Bennée wrote:
> I did run the make under strace to see who is using O_NONBLOCK but even
> after filtering out a bunch of stuff it seems to be quite embedded:
>
> ag "O_NONBLOCK" check.strace | ag -v "/sys" | ag -v "/dev" | grep -v ".git"
> | wc -l
> 2449
Hi,
So trying to narrow down the remaining failures in the CI system. There
is one with a patch in flight (use g_usleep instead of sleep) but there
remains two failure modes, both erratic.
tests/qht-par:
I can trigger this on my dev machine with a gprof enabled build:
# QEMU configure log
