Re: Issue with checks after 2.0.6

2019-09-15 Thread GARDAIS Ionel
Hi Lukas, Same with nbthread 1. I gave my first try to git bisect and it looks like the offending commit is : ab160a47acde9dc9c341b328c8716a721a389ab4 is the first bad commit commit ab160a47acde9dc9c341b328c8716a721a389ab4 Author: Willy Tarreau Date: Thu Sep 5 17:38:40 2019 +0200 BUG/MIN

Re: BUG/MEDIUM: spoe: engine-id is necessary if not health check

2019-09-15 Thread Kevin Zhu
Sorry Crhistopher, have you look at this mail ?😁 On Mon, 2 Sep 2019 at 16:11, Kevin Zhu wrote: > Hi Christopher > > SPOE engine-id is all same when nbproc is more than 1, the clients all > group under same engine, and same stream-id and frame-id frames may come > at > same time. So we alway need

Re: Issue with checks after 2.0.6

2019-09-15 Thread Lukas Tribus
Hello, On Sat, Sep 14, 2019 at 4:58 PM GARDAIS Ionel wrote: > > What was the previous release that worked for you? 2.0.5 or something older? > > 2.0.5 worked well from the checks point of vue. Ok, so this is a regression in 2.0.6. Please try whether limiting the threads to 1 (global section: nb

Re: Linux Builds broken on Travis CI

2019-09-15 Thread Willy Tarreau
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*