On Sat, Sep 14, 2019 at 09:20:53PM +0500, ??? wrote:
> it turned out that ASAN is "the root cause" of those failures. let us
> disable it for a while (I attached patch)
OK now merged but I really fail to see the relation between ASAN and
the random "out of memory" errors spewed by *vtest*
it turned out that ASAN is "the root cause" of those failures. let us
disable it for a while (I attached patch)
пт, 13 сент. 2019 г. в 19:23, Илья Шипицин :
>
>
> On Fri, Sep 13, 2019, 3:49 PM Willy Tarreau wrote:
>
>> On Fri, Sep 13, 2019 at 03:45:21PM +0500, ??? wrote:
>> > now build
On Fri, Sep 13, 2019, 3:49 PM Willy Tarreau wrote:
> On Fri, Sep 13, 2019 at 03:45:21PM +0500, ??? wrote:
> > now build fails with
> >
> > "** h1 debug|[ALERT] 255/081449 (8721) : failed to allocate resources for
> > thread 1."
>
> That's exactly the issues I was talking about that start
On Fri, Sep 13, 2019 at 03:45:21PM +0500, ??? wrote:
> now build fails with
>
> "** h1 debug|[ALERT] 255/081449 (8721) : failed to allocate resources for
> thread 1."
That's exactly the issues I was talking about that started to happen
at an increasing frequency over the last few weeks.
now build fails with
"** h1 debug|[ALERT] 255/081449 (8721) : failed to allocate resources for
thread 1."
no more failures due to leaks.
пт, 13 сент. 2019 г. в 13:33, Willy Tarreau :
> On Fri, Sep 13, 2019 at 01:23:12PM +0500, ??? wrote:
> > Build was failed due to memory leak detec
On Fri, Sep 13, 2019 at 01:23:12PM +0500, ??? wrote:
> Build was failed due to memory leak detected by asan
>
> https://github.com/haproxy/haproxy/issues/256
>
>
> I think we can change the way asan works, I.e. log errors and do not stop
> tests
I didn't even notice it was this one bec
Build was failed due to memory leak detected by asan
https://github.com/haproxy/haproxy/issues/256
I think we can change the way asan works, I.e. log errors and do not stop
tests
On Fri, Sep 13, 2019, 7:59 AM Willy Tarreau wrote:
> Hi Tim,
>
> On Fri, Sep 06, 2019 at 04:30:24PM +0200, Tim D
Hi Tim,
On Fri, Sep 06, 2019 at 04:30:24PM +0200, Tim Düsterhus wrote:
> Dear List
>
> something between 02bac85bee664976f6dcecc424864e9fb99975be and
> f909c91e8a739b9ef7409b399259201fe883771c broke all the Linux builds on
> Travis CI:
>
> - 41 reg tests fail with a timeout
> - 3 reg tests pass
Dear List
something between 02bac85bee664976f6dcecc424864e9fb99975be and
f909c91e8a739b9ef7409b399259201fe883771c broke all the Linux builds on
Travis CI:
- 41 reg tests fail with a timeout
- 3 reg tests pass
FreeBSD works fine.
Somebody really ought to take a look. I might try to bisect if I f
9 matches
Mail list logo