вт, 3 нояб. 2020 г. в 13:51, William Lallemand <[email protected]>:
> On Mon, Nov 02, 2020 at 05:17:53PM +0500, Илья Шипицин wrote: > > сб, 31 окт. 2020 г. в 17:53, Willy Tarreau <[email protected]>: > > > > > Hi, > > > > > > HAProxy 2.3-dev9 was released on 2020/10/31. It added 27 new commits > > > after version 2.3-dev8. > > > > > > Things have cooled down quite a bit, I really appreciate it. To be > > > honest, I've really been hesitating between releasing 2.3-final now > > > or leaving one extra week. Finally, considering that we're not late > > > and that the last fixed issues were recently reported, I considered > > > that it was worth waiting one more week to confirm this encouraging > > > trend. > > > > > > > freebsd builds are unstable > > https://github.com/haproxy/haproxy/runs/1341524534 > > > > That one is strange, it looked like the proxy protocol is working since > there are others tests which use it that works. However this is the only > test in the reg-test suite using "unix@" maybe the issue is here, or a > combination of the two. > > > also, couple of reg-tests fail on openssl no-deprecated mode > > https://github.com/haproxy/haproxy/issues/924 > > > > I don't know about this one, I'll need to test that locally, I never > linked haproxy with the no-deprecated mode before, I don't even know if > workflow file .github/workflows/openssl-nodeprecated.yml might be used for build commands to link locally. it is just one build time define. > every haproxy features are supported with this mode. > > > > > should we address those failures before 2.3 release ? > > > > It's better if we can fix the FreeBSD issue and at least identify what > the problems are with the openSSL issue. > > -- > William Lallemand >
