Hi Pieter,

On Thu, Sep 13, 2018 at 05:13:43PM +0200, PiBa-NL wrote:
> Just tried another run of regtests on FreeBSD, and found that lua/b00002.vtc
> fails (coredump, gdb bt below) with todays snapshot: HA-Proxy version
> 1.9-dev2-253006d 2018/09/12

Yesterday we've looked at this with Olivier and it raised some questions
between us regarding the nature of certain events that need to be reported
upwards. Here the issue is related to the sequencing of the connect_server()
call and the subscription to try to receive. If we do it the current way,
we read from a non-existent mux and if we do it the other way around we'll
lose connect events if there's no data to send. We have some plans for this
that we're discussing today in front of the white board. Getting rid of ~15
years of accumulated hacks in the connection layers is amazingly difficult,
and much more than what it looks like before trying to do it!

I hope that today we'll have clear ideas about a very short-term workaround
and how we want to address this situation from an architecture perspective.

> p.s. should reg-tests maybe get run before the -dev releases get tagged? (or
> is that already done, and this could be a FreeBSD specific issue and as such
> not have been spotted?)

It's my fault. Yes I'm supposed to run these tests. But after finally
managed to collect all the long-awaited code a few minutes before I really
had to leave, I was impatient to push it out so that we can all resync. And
not having vtc anymore after I rebooted my PC (last time it was built in
/dev/shm and I still didn't take the time to rebuild it) didn't give me
enough motivation to add this extra task. The process will improve over
time, we need it to become more natural and usual. You don't kill 18
years of bad habits in a few weeks! Just to be clear, spotting bugs at
this moment will not prevent me from emitting a dev release, but at least
I'll report them in the changelog so that nobody wastes their time ;-)

Cheers,
Willy

Reply via email to