On Thu, Jan 07, 2021 at 11:03:14AM +0100, William Dauchy wrote:
> On Wed, Jan 6, 2021 at 5:45 PM Willy Tarreau <w...@1wt.eu> wrote:
> > HAProxy 2.4-dev5 was released on 2021/01/06. It added 91 new commits
> > after version 2.4-dev4.
> 
> unclear whether this is on my side only because I did not investigate
> but I have two tests failing for a while now:
> 
> ########################## Starting vtest ##########################
> Testing with haproxy version: 2.4-dev5-761d64-4
> #    top  TEST reg-tests/filters/random-forwarding.vtc FAILED (0.192) exit=2
> #    top  TEST reg-tests/seamless-reload/abns_socket.vtc FAILED (2.215) exit=2

I didn't observe them, they all succeed on my side, and just checking
the CI, it seems they succeed. But that doesn't mean they're reliable
or anything, very often regtests start to fail sporadically in a single
environment before we figure the problem.

Is it 100% reproducible for you ?

> 2 tests failed, 0 tests skipped, 106 tests passed
> ########################## Gathering results ##########################
> ###### Test case: reg-tests/seamless-reload/abns_socket.vtc ######
> ## test results in:
> "/tmp/haregtests-2021-01-07_10-59-10.xOIJpc/vtc.115543.67e5fada"
> ---- h1   Bad exit status: 0x0000 exit 0x0 signal 0 core 0
> ###### Test case: reg-tests/filters/random-forwarding.vtc ######
> ## test results in:
> "/tmp/haregtests-2021-01-07_10-59-10.xOIJpc/vtc.115543.72f8fd5f"
> ---- c1   Assert error in vtc_gunzip(), src/vtc_gzip.c line 114:
> Condition(vz.total_out < l) not true.  Errno=0 Success

I remember seeing this one with an old version of vtest, and it
went away after an upgrade.

> I build with:
> 
> make -j5 CPU="generic" TARGET="linux-glibc" USE_OPENSSL=1 USE_PCRE=1
> USE_PCRE_JIT=1 USE_ZLIB=1 USE_GETADDRINFO=1 USE_LINUX_TPROXY=1
> ADDLIB="-ljemalloc" DEFINE=-DTCP_USER_TIMEOUT=18 USE_SYSTEMD=1
> USE_TFO=1 USE_NS=1
> EXTRA_OBJS="contrib/prometheus-exporter/service-prometheus.o"

Using the exact same options (except systemd) worked fine for me
with 106 successful tests. So at least it's not cause exclusively
by the set of options.

Willy

Reply via email to