Hi Aleks, Thanks you to have integrate BoringSSL!
> Le 29 mars 2019 à 14:51, Aleksandar Lazic <al-hapr...@none.at> a écrit : > > Am 29.03.2019 um 14:25 schrieb Willy Tarreau: >> Hi Aleks, >> >> On Fri, Mar 29, 2019 at 02:09:28PM +0100, Aleksandar Lazic wrote: >>> With openssl are 2 tests failed but I'm not sure because of the setup or a >>> bug. >>> https://gitlab.com/aleks001/haproxy19-centos/-/jobs/186769272 >> >> Thank you for the quick feedback. I remember about the first one being >> caused by a mismatch in the exact computed response size due to headers >> encoding causing some very faint variations, though I have no idea why >> I don't see it here, since I should as well, I'll have to check my regtest >> script. For the second one, it looks related to the reactivation of the >> HEAD method in this test which was broken in previous vtest. But I'm >> seeing in your trace that you're taking it from the git repo so that >> can't be that. I need to dig as well. >> >>> With boringssl are 3 tests failed but I'm not sure because of the setup or >>> a bug. >>> https://gitlab.com/aleks001/haproxy-19-boringssl/-/jobs/186780822 >> >> For this one I don't know, curl reports some unexpected EOFs. I don't >> see why it would fail only with boringssl. Did it use to work in the >> past ? > > No. The tests with Boringssl always failed in one or another way. > It’s strange. After quick test, it works in my environnements. I need to comment "${no-htx} option http-use-htx » to test with varnishtest. > https://gitlab.com/aleks001/haproxy-19-boringssl/-/jobs/157743825 > <https://gitlab.com/aleks001/haproxy-19-boringssl/-/jobs/157743825> > https://gitlab.com/aleks001/haproxy-19-boringssl/-/jobs/157730793 > <https://gitlab.com/aleks001/haproxy-19-boringssl/-/jobs/157730793> > > I'm not sure if the docker setup on gitlab is the limitation or just a bug. > Sorry to be so unspecific. > >> Thanks, >> Willy > > Regards > Aleks ++ Manu
