вт, 23 апр. 2019 г. в 14:50, Willy Tarreau :
> Hi Tim,
>
> On Tue, Apr 23, 2019 at 11:28:22AM +0200, Tim Düsterhus wrote:
> > No real management necessary.
> (...)
> > Ideally you should not notice anything: It means no one commited bad
> > code. It might need some adjustments in the beginning, ve
let us wait for a while and do not enable "allow failures".
вт, 23 апр. 2019 г. в 20:24, Willy Tarreau :
> On Tue, Apr 23, 2019 at 04:41:44PM +0200, Tim Düsterhus wrote:
> > List,
> >
> > Am 23.04.19 um 16:40 schrieb Tim Duesterhus:
> > > [...]
> >
> > Sorry for the noise. This v2 only differs by
I want to bisect in order to find offending commit.
we've got regression. it need to be fixed, no need to mark it as "allowed
failure"
вт, 23 апр. 2019 г. в 22:00, Willy Tarreau :
> On Tue, Apr 23, 2019 at 09:20:52PM +0500, ??? wrote:
> > let us wait for a while and do not enable "allow
-ci.com/haproxy/haproxy/builds/109289462
вт, 23 апр. 2019 г. в 22:11, Илья Шипицин :
> I want to bisect in order to find offending commit.
> we've got regression. it need to be fixed, no need to mark it as "allowed
> failure"
>
> вт, 23 апр. 2019 г. в 22:00, Willy
this particular regression is reproduced on my fedora laptop, which is
openssl-1.1.X
вт, 23 апр. 2019 г. в 22:31, Willy Tarreau :
> On Tue, Apr 23, 2019 at 10:11:09PM +0500, ??? wrote:
> > I want to bisect in order to find offending commit.
> > we've got regression. it need to be fixed,
yep, I'm going to invest some time in building openssl matrix on travis-ci,
i.e. openssl-1.0, 1.0.2, 1.1.1, libressl, ...
вт, 23 апр. 2019 г. в 22:31, Willy Tarreau :
> On Tue, Apr 23, 2019 at 10:11:09PM +0500, ??? wrote:
> > I want to bisect in order to find offending commit.
> > we've
вт, 23 апр. 2019 г. в 23:25, Willy Tarreau :
> On Tue, Apr 23, 2019 at 10:31:05PM +0500, ??? wrote:
> > Hello, Baptise!
> >
> > we have enabled travis-ci builds on haproxy master branch. seems we have
> a
> > regression here:
> >
> >
> http://git.haproxy.org/?p=haproxy.git;a=commit;h=3339
Hello,
I'm going to use various sanitizers, for example CFLAGS="-fsanitize=address"
I'm looking for preferred way to set additional CFLAGS, am I right that it
is something like ADDINC="-fsanitize=address" ? any other way ?
thanks!
Ilya Shipitsin
I'd accept "Extend .travis.yml" patch except "allow_failures"
Tim, do you mind to send "v2" ?
ср, 24 апр. 2019 г. в 17:45, Willy Tarreau :
> Hi Ilya,
>
> On Tue, Apr 23, 2019 at 09:37:27PM +0200, Willy Tarreau wrote:
> > On Wed, Apr 24, 2019 at 12:30:36AM +0500, ??? wrote:
> > > >
> htt
I've managed to pass sanitizer flags )) I will add something like that to
travis-ci later
*** h10.1 debug|==19083==ERROR: AddressSanitizer:
global-buffer-overflow on address 0x00a8cda8 at pc 0x006efec0 bp
0x7ffc78cfc990 sp 0x7ffc78cfc988
*** h10.1 debug|READ of size 8 at 0x
here's "v2"
ср, 24 апр. 2019 г. в 18:56, Илья Шипицин :
> I can test myself and send "v2" in couple of hours if you do not mind
>
> ср, 24 апр. 2019 г. в 18:48, Tim Düsterhus :
>
>> Willy,
>> Ilya,
>>
>> I'm not in the office tod
ср, 24 апр. 2019 г. в 19:21, Илья Шипицин :
> here's "v2"
>
> ср, 24 апр. 2019 г. в 18:56, Илья Шипицин :
>
>> I can test myself and send "v2" in couple of hours if you do not mind
>>
>> ср, 24 апр. 2019 г. в 18:48, Tim Düsterhus :
>>
ns of logs. The
> details can then be found collapsed at the bottom.
>
> Best regards
> Tim Düsterhus
>
> Am 24.04.2019 16:59 schrieb Илья Шипицин :
>
> Tim, I'm bit curious about
>
> after_failure:
> - |
> for folder in ${TMPDIR:-/tmp}/*regtest*/vtc.*; do
>
Yes, I did have a look as well, those failures did not look like something
we would wish to ignore ))
Also, I'd suggest to extend osx build to include more features. I will do
it soon
On Thu, Apr 25, 2019, 12:00 PM Willy Tarreau wrote:
> On Thu, Apr 25, 2019 at 08:26:37AM +0200, Willy Tarreau w
please have a look
build script:
https://github.com/chipitsine/haproxy-1/commit/6739f36463dc9e82eb65a9fa8353a42128403f0c
build log (error):
https://api.cirrus-ci.com/v1/task/5196617547251712/logs/main.log
any idea ?
thanks!
Ilya Shipicin
Hi,
I tested the following patch on LibreSSL-2.7.5, 2.8.3, 2.9.1
thanks!
Ilya Shipitcin
From 12c3a7b0eac4bab73864869bf8fcb365c9ba06ef Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Sun, 28 Apr 2019 00:00:16 +0500
Subject: [PATCH] BUILD: add defines to support LibreSSL tested on
LibreSSL-2.
here's build log
https://travis-ci.org/chipitsine/haproxy-1/builds/525403732
вс, 28 апр. 2019 г. в 00:04, Илья Шипицин :
> Hi,
>
> I tested the following patch on LibreSSL-2.7.5, 2.8.3, 2.9.1
>
> thanks!
> Ilya Shipitcin
>
3) run freebsd builds in "build only mode", no reg tests
4) ...
пн, 29 апр. 2019 г. в 18:36, Frederic Lecaille :
> On 4/29/19 2:18 PM, Frederic Lecaille wrote:
> > On 4/27/19 1:28 AM, Илья Шипицин wrote:
> >> please have a look
> >>
> >>
> >&g
OWN."
} -start
it works, test is green now (on freebsd)
https://cirrus-ci.com/task/6252507322908672
пн, 29 апр. 2019 г. в 19:14, Frederic Lecaille :
> On 4/29/19 3:56 PM, Илья Шипицин wrote:
> > well, in cirrus-ci we can choose several freebsd images. I just picked
> > up
вт, 30 апр. 2019 г. в 13:32, Frederic Lecaille :
> On 4/30/19 10:04 AM, Илья Шипицин wrote:
> > Hello, Frederic
> >
> > I have applied only that part
> >
> > barrier b cond 3
> > @@ -29,7 +30,7 @@ syslog S3 -level notice {
> > recv
> >
you are right.
let us exclude that particular test from freebsd (what your patch exactly
does)
вт, 30 апр. 2019 г. в 13:57, Илья Шипицин :
>
>
> вт, 30 апр. 2019 г. в 13:32, Frederic Lecaille :
>
>> On 4/30/19 10:04 AM, Илья Шипицин wrote:
>> > Hello, Frederic
>>
It still fails on 12, I applied patch, run test.
So, I suggest to disable it
On Tue, Apr 30, 2019, 2:43 PM Frederic Lecaille
wrote:
> On 4/30/19 11:24 AM, Илья Шипицин wrote:
> > you are right.
> >
> > let us exclude that particular test from freebsd (what your patch
>
Hello.
I enabled basic freebsd CI (yet, it need to be enabled on github.com in few
easy steps)
thanks!
Ilya Shipitcin
From c0feb90929b1e8f1987dde27fc9f57c9b6d8fc36 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Tue, 30 Apr 2019 15:33:36 +0500
Subject: [PATCH] BUILD: enable freebsd builds on
Hello,
typo was found by cppcheck
thank!
Ilya Shipitsin
From 62c6b78843e9c1b6f829872a54175f68332a2859 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Tue, 30 Apr 2019 21:21:28 +0500
Subject: [PATCH] MINOR: fix typo "src" instead of "srv"
---
src/server.c | 2 +-
1 file changed, 1 insertion
Hello,
I'm expanding openssl matrix.
here's failing build
https://travis-ci.org/chipitsine/haproxy-1/jobs/527683332
пт, 3 мая 2019 г. в 18:33, Frederic Lecaille :
> On 5/3/19 1:34 PM, Tim Düsterhus wrote:
> > Fred,
> > Ilya,
>
> Hello Tim,
>
> > Am 03.05.19 um 13:20 schrieb Frederic Lecaille:
> >> About the test which fail, I would say that such errors are not
> >> negligible :
> >>
> >> Starting frontend
пт, 3 мая 2019 г. в 18:42, Tim Düsterhus :
> Ilya,
>
> Am 03.05.19 um 15:39 schrieb Илья Шипицин:
> > when I played with enabling travis-ci, I tried to set TMPDIR directly,
> > however I was not lucky enough.
> > Later Tim added "sed" magic to .travis.yml
&g
Hello,
I run reg-tests on gcc-9 (fedora 30).
I built haproxy the following way
make CC=gcc V=1 TARGET=$TARGET $FLAGS DEBUG_CFLAGS="-fsanitize=address
-ggdb" LDFLAGS="-lasan"
asan found couple of things
*** h10.1 debug|#0 0x6db986 in update_log_hdr src/log.c:1399
*** h10.1 debug|
I would even use shorter path, i.e.
mkdir ~/t
пт, 3 мая 2019 г. в 22:27, Frederic Lecaille :
> On 5/3/19 5:35 PM, Frederic Lecaille wrote:
> > On 5/3/19 3:44 PM, Илья Шипицин wrote:
> >>
> >>
> >> пт, 3 мая 2019 г. в 18:42, Tim Düsterhus >> <m
libressl is known to present "bigger than openssl-1.1.1" version (while
lacking many features)
let us wait for libressl+travis-ci patch approval
сб, 4 мая 2019 г. в 00:09, Olivier Houchard :
> Hi Igor,
>
> On Fri, May 03, 2019 at 05:21:50PM +0800, Igor Pav wrote:
> > Just tested with openssl 1.1.
nice, I will add sanitizers to travis-ci matrix
вс, 5 мая 2019 г. в 13:18, Willy Tarreau :
> Hi Ilya,
>
> On Fri, May 03, 2019 at 06:58:19PM +0500, ??? wrote:
> > *** h10.1 debug|#0 0x6db986 in update_log_hdr src/log.c:1399
> (...)
> > *** h10.1 debug|previously allocated b
can we also apply patch from
https://www.mail-archive.com/haproxy@formilux.org/msg33439.html ?
it should repair libressl builds
вс, 5 мая 2019 г. в 13:25, Willy Tarreau :
> On Fri, May 03, 2019 at 10:23:05AM +, PR Bot wrote:
> > Description:
> >added openssl-1.0.2, 1.1.0, 1.1.1, libressl-
Hello,
I run fedora 30, it includes clang-8, I built haproxy using
make CC=clang V=1 TARGET=$TARGET $FLAGS DEBUG_CFLAGS="-fsanitize=address
-ggdb" LDFLAGS="-fsanitize=address"
when running reg-tests, the following is caught
==6340==ERROR: AddressSanitizer: global-buffer-overflow on address
0x00
something has changed. build is passing now, reg-tests fail (they used to
work earlier)
I'd apply those patches (and we will fix reg-tests later)
вс, 5 мая 2019 г. в 15:51, Willy Tarreau :
> On Sun, May 05, 2019 at 02:26:11PM +0500, ??? wrote:
> > can we also apply patch from
> > https
with sanitizer:
$ objdump -h haproxy
haproxy: file format elf64-x86-64
Sections:
Idx Name Size VMA LMA File off
Algn
0 .interp 001c 004002e0 004002e0 02e0
2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
г. в 23:29, Илья Шипицин :
> something has changed. build is passing now, reg-tests fail (they used to
> work earlier)
>
>
> I'd apply those patches (and we will fix reg-tests later)
>
> вс, 5 мая 2019 г. в 15:51, Willy Tarreau :
>
>> On Sun, May 05, 2019 at 0
hello,
when I first sent LibreSSL patches (it was 27th April 2019), reg-tests were
ok.
I suspect recent 0RTT patches could break LibreSSL things
can someone have a look ?
https://travis-ci.org/chipitsine/haproxy-1/builds/528535120
thanks!
Ilya Shipitcin
well, I hope travis-ci will be useful (or we will drop it).
as for PR, I meant that it should have been sent to list anyway (but it was
not sent for some reason).
I can send using "git send email" as well
пн, 6 мая 2019 г. в 11:05, Willy Tarreau :
> Hi Ilya,
>
> > I made another PR
> >
> > https
there's some random failure
https://travis-ci.com/haproxy/haproxy/jobs/197824840
looks like test is not stable
пн, 6 мая 2019 г. в 11:11, Willy Tarreau :
> On Sun, May 05, 2019 at 10:11:38PM +0200, Frederic Lecaille wrote:
> > I had no access to any travis environment when it has been told in
>
surprisingly, LibreSSL builds are green
пн, 6 мая 2019 г. в 13:03, Willy Tarreau :
> On Mon, May 06, 2019 at 12:54:06PM +0500, ??? wrote:
> > there's some random failure
> >
> > https://travis-ci.com/haproxy/haproxy/jobs/197824840
> >
> > looks like test is not stable
>
> isn't it th
I have just noticed that "scripts/build-ssl.sh" is missing in .travis.yml
so, unfortunately, we are running all builds against xenial openssl-1.0.2
(no openssl-1.1.X, no libressl...)
I'm not sure when "scripts/build-ssl.sh" disappeared. I'll send new patch
soon
пн, 6 мая 2019 г. в 11:05, Willy Ta
Hello,
I built haproxy using gcc-9
make CC=gcc V=1 TARGET=linux2628 USE_ZLIB=1 USE_PCRE=1 USE_PCRE_JIT=1
USE_LUA=1 USE_OPENSSL=1 DEBUG_CFLAGS="-g -fsanitize=address"
LDFLAGS="-lasan"
finding is:
*** h10.1 debug|==8326==ERROR: LeakSanitizer: detected memory leaks
*** h10.1 debug|
***
Hello,
when running regtests against 1.9 branch there are findings (not seen in
master branch)
*** h10.0
debug|=
*** h10.0 debug|==16493==ERROR: AddressSanitizer: heap-use-after-free
on address 0x61903c95 at pc 0x00
travis-ci supports windows builds. I will add such build a bit later (after
we settle with current travis-ci fixes)
ср, 8 мая 2019 г. в 10:52, Willy Tarreau :
> Hi,
>
> On Mon, May 06, 2019 at 12:54:47PM +0300, Gil Bahat wrote:
> > Hi,
> >
> > is cygwin still supported anymore?
>
> Well, we never
ср, 8 мая 2019 г. в 11:06, Willy Tarreau :
> On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote:
> > travis-ci supports windows builds.
>
> cool!
>
my current roadmap is
1) patch fixes SSL variants (already sent to list). without it we are NOT
building LibreSSL at all (i.e. we use defa
small fix
ср, 8 мая 2019 г. в 11:12, Willy Tarreau :
> On Wed, May 08, 2019 at 11:09:04AM +0500, ??? wrote:
> > ??, 8 ??? 2019 ?. ? 11:06, Willy Tarreau :
> >
> > > On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote:
> > > > travis-ci supports windows builds.
> > >
> > > cool!
I messed up with commit message. One more try
ср, 8 мая 2019 г. в 11:33, Илья Шипицин :
> small fix
>
> ср, 8 мая 2019 г. в 11:12, Willy Tarreau :
>
>> On Wed, May 08, 2019 at 11:09:04AM +0500, ??? wrote:
>> > ??, 8 ??? 2019 ?. ? 11:06, Willy Tarreau :
>&
I would like to run sanitizers before new 1.9 release is out
On Wed, May 8, 2019, 10:54 AM Willy Tarreau wrote:
> Hi Ilya,
>
> On Tue, May 07, 2019 at 11:47:54AM +0500, ??? wrote:
> > Hello,
> >
> > when running regtests against 1.9 branch there are findings (not seen in
> > master bran
ср, 8 мая 2019 г. в 13:03, Willy Tarreau :
> Hi Ilya,
>
> On Wed, May 08, 2019 at 11:34:57AM +0500, ??? wrote:
> > From ad9961e92c692430272c9088a49759c889dac6f1 Mon Sep 17 00:00:00 2001
> > From: Ilya Shipitsin
> > Date: Wed, 8 May 2019 11:32:02 +0500
> > Subject: [PATCH] BUILD: do not u
Frederic, can you help with some "haproxy reg test getting started" doc ?
ср, 8 мая 2019 г. в 13:13, Илья Шипицин :
>
>
> ср, 8 мая 2019 г. в 13:03, Willy Tarreau :
>
>> Hi Ilya,
>>
>> On Wed, May 08, 2019 at 11:34:5
ср, 8 мая 2019 г. в 13:55, Willy Tarreau :
> On Wed, May 08, 2019 at 01:13:56PM +0500, ??? wrote:
> > > libressl ? My understanding of this thing is that this problem is not
> > > easy to detect by accident and causes a mess for people who reload
> often.
> > > If libressl is affected by
ср, 8 мая 2019 г. в 14:50, Willy Tarreau :
> On Wed, May 08, 2019 at 02:06:31PM +0500, ??? wrote:
> > > Ilya, could you please instead change the test like this and test
> again :
> > >
> > > -#if defined(USE_OPENSSL) && (OPENSSL_VERSION_NUMBER >= 0x10101000L)
> > > +#if defined(USE_OPENS
Hello,
does haproxy have some issues when it is built using openssl-1.1.0 and
running with openssl-1.1.1, for example ?
should we consider such situations in travis-ci openssl matrix ?
thanks!
Ilya Shipitsin
osx build is broken
https://travis-ci.com/haproxy/haproxy/jobs/199157750
seems to be related
пт, 10 мая 2019 г. в 14:45, Chris Packham :
> __ha_cas_dw() is used in fd_rm_from_fd_list() and when built without
> USE_THREADS=1 the linker fails to find __ha_cas_dw(). Add a definition
> of __ha_cas_
this patch will reveal osx reg-tests errors (after osx build is repaired)
пт, 10 мая 2019 г. в 15:38, :
> From: Ilya Shipitsin
>
> v2, rebased to master
>
> ---
> .travis.yml | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index c00725d8
please ignore, I will send "v2" soon
пт, 10 мая 2019 г. в 15:32, :
> From: Ilya Shipitsin
>
> ---
> .travis.yml | 8 ++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index f9a13586..530d1682 100644
> --- a/.travis.yml
> +++ b/.travis.yml
>
I tested, everything is ok
пн, 13 мая 2019 г. в 20:24, Tim Duesterhus :
> Oops, my patch was incomplete, because I noticed that I missed one
> location after creating the commit and forgot to amend after making
> the necessary adjustments.
>
> So here's version 2 that fixes the leak on SIGTERM in
Hello,
can we enable cirrus-ci ? it's like travis-ci, it allows run freebsd builds
ср, 1 мая 2019 г. в 14:11, Илья Шипицин :
> hello!
>
> can you please enable cirrus-ci on https://github.com/haproxy/haproxy ?
>
>
> -- Forwarded message -
> От: Илья Ш
чт, 16 мая 2019 г. в 02:02, Aleksandar Lazic :
> Am 15.05.2019 um 18:52 schrieb Willy Tarreau:
> > Hi,
> >
> > HAProxy 2.0-dev3 was released on 2019/05/15. It added 393 new commits
> > after version 2.0-dev2.
> >
> > This is another huge version, having been distacted by a number of bugs
> > latel
Hello,
I'm going to enable address sanitizer in travis-ci.
x86_64: (known leak)
https://travis-ci.org/chipitsine/haproxy-1/jobs/533196875
ppc64le:
https://travis-ci.org/chipitsine/haproxy-1/jobs/533196874
can someone have a look at ppc64le ?
thanks!
Ilya Shipitsin
чт, 16 мая 2019 г. в 12:42, Willy Tarreau :
> Hi Ilya,
>
> On Thu, May 16, 2019 at 01:12:40AM +0500, ??? wrote:
> > in order to enable builds, the following steps must be taken
> >
> > 1) must be enabled (using owner account) on
> > https://github.com/marketplace/cirrus-ci , also "haproxy
чт, 16 мая 2019 г. в 22:53, Tim Düsterhus :
> Willy,
>
> Am 16.05.19 um 09:42 schrieb Willy Tarreau:
> > If in the mean time you know how to verify that it was properly enabled
> > and builds there, and share with us the link to consult the status, it
> > would be nice.
>
> These continuous integr
чт, 16 мая 2019 г. в 22:59, Tim Düsterhus :
> Willy,
>
> Am 16.05.19 um 09:42 schrieb Willy Tarreau:
> > It would be nice next time to give a bit more information. Maybe for
> > you this cirrus stuff is legacy, but I never heard about it before, am
> > not used at all to this type of tools, and do
чт, 16 мая 2019 г. в 23:22, Tim Düsterhus :
> Aleks,
>
> Am 16.05.19 um 01:04 schrieb Aleksandar Lazic:
> >> As a avid Docker user: I tend to absolutely avoid any Docker images that
> >> are not built using Docker Hub's autobuilder, because I cannot verify
> >> the Dockerfile myself (or cannot ver
пт, 17 мая 2019 г. в 11:57, Willy Tarreau :
> Hi Ilya,
>
> On Thu, May 16, 2019 at 02:04:06PM +0500, ??? wrote:
> > Hello,
> >
> > I'm going to enable address sanitizer in travis-ci.
> >
> > x86_64: (known leak)
> > https://travis-ci.org/chipitsine/haproxy-1/jobs/533196875
> >
> > ppc64le
пт, 17 мая 2019 г. в 13:39, Aleksandar Lazic :
> Am 16.05.2019 um 10:00 schrieb Илья Шипицин:
> >
> > чт, 16 мая 2019 г. в 02:02, Aleksandar Lazic > <mailto:al-hapr...@none.at>>:
> >
> > Am 15.05.2019 um 18:52 schrieb Willy Tarreau:
> > > H
ExaBGP ?
пн, 20 мая 2019 г. в 20:01, Jeff Abrahamson :
> Thanks. Have you tried that, bringing down an haproxy during some high
> load period and watching traffic to see how long it takes for traffic all
> to migrate to the remaining haproxy? My fear (see below) is that that time
> is quite lon
here's build with patch applied
https://travis-ci.org/chipitsine/haproxy-1/jobs/535709947#L604-L608
ср, 22 мая 2019 г. в 14:43, William Lallemand :
> Hi Tim,
>
> Sorry for the delay.
>
> I added 2 new lines in your patch:
>
> On Thu, May 16, 2019 at 08:23:22PM +0200, Tim Duesterhus wrote:
> > +v
more findings
https://travis-ci.org/chipitsine/haproxy-1/jobs/535709949#L1938-L1948
ср, 22 мая 2019 г. в 15:12, Илья Шипицин :
> here's build with patch applied
>
> https://travis-ci.org/chipitsine/haproxy-1/jobs/535709947#L604-L608
>
> ср, 22 мая 2019 г. в 14:43, William
Hello,
someone is reviewing this https://github.com/haproxy/haproxy/runs/133866993
?
thanks,
Ilya Shipitcin
build is green now, we can apply this patch (I skipped "linux-ppc64le" for
a while)
ср, 22 мая 2019 г. в 18:37, :
> From: Ilya Shipitsin
>
> full list of changes:
>
> use TARGET=osx instead of generic for osx builds,
> add USE_PCRE_JIT=1, USE_GETADDRINFO=1 to build matrix,
> enable address sanit
ср, 22 мая 2019 г. в 19:18, Willy Tarreau :
> Hi Ilya,
>
> On Wed, May 22, 2019 at 06:37:58PM +0500, ??? wrote:
> > build is green now, we can apply this patch (I skipped "linux-ppc64le"
> for
> > a while)
>
> It's really easier for me if you attach it again. I'm getting about 2k
> emails
done
ср, 22 мая 2019 г. в 19:18, Willy Tarreau :
> Hi Ilya,
>
> On Wed, May 22, 2019 at 06:37:58PM +0500, ??? wrote:
> > build is green now, we can apply this patch (I skipped "linux-ppc64le"
> for
> > a while)
>
> It's really easier for me if you attach it again. I'm getting about 2k
>
Hello,
if we do not like using github PR and Willy receives 2k emails a day...
do we consider using something like that
https://patchwork.openvpn.net/project/openvpn2/list/ ?
cheers,
Ilya Shipitsin
чт, 23 мая 2019 г. в 14:03, Willy Tarreau :
> On Wed, May 22, 2019 at 07:15:21PM +0200, Willy Tarreau wrote:
> > On Wed, May 22, 2019 at 03:24:25PM +0500, ??? wrote:
> > > Hello,
> > >
> > > someone is reviewing this
> https://github.com/haproxy/haproxy/runs/133866993
> > > ?
> >
> > So a
чт, 23 мая 2019 г. в 01:28, Willy Tarreau :
> Hi,
>
> HAProxy 2.0-dev4 was released on 2019/05/22. It added 83 new commits
> after version 2.0-dev3.
>
> This release completes the integration of a few pending features and
> the ongoing necessary cleanups before 2.0.
>
> A few bugs were addressed i
чт, 23 мая 2019 г. в 18:45, Willy Tarreau :
> On Thu, May 23, 2019 at 04:17:33PM +0500, ??? wrote:
> > I'd like to run sanitizers on vaious combinations, like ZLIB / SLZ, PCRE
> /
> > PCRE2 ...
> > ok, let us do it before Wednesday
>
> OK, why not. Feel free to send patches once you can t
hello,
memory leak was found by valgrind
From 61f04a8ecdcfc105f732d5978180ad2ab746cc34 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Sat, 25 May 2019 03:38:14 +0500
Subject: [PATCH] BUG/MINOR: ssl_sock: Fix memory leak when disabling
compression
according to manpage:
sk_TYPE_zero(
hi, I see it it not yet applied.
it turned out that freeing breaks LibreSSL internals.
so, here's v2 (free only if not LibreSSL)
сб, 25 мая 2019 г. в 10:46, Willy Tarreau :
> Hi Ilya,
>
> > From 61f04a8ecdcfc105f732d5978180ad2ab746cc34 Mon Sep 17 00:00:00 2001
> > From: Ilya Shipitsin
> > Date
I came with a better patch
actually it is not required to free compression methods on OpenSSL >= 1.0.0
so, let us only do that when it is really neccessary
сб, 25 мая 2019 г. в 14:59, Илья Шипицин :
> hi, I see it it not yet applied.
> it turned out that freeing breaks LibreSSL intern
Hello,
I added freebsd-11 to cirrus-ci
https://cirrus-ci.com/task/5162023978008576
should we fix it before 2.0 release ?
cheers,
Ilya Shipitsin
ср, 29 мая 2019 г. в 07:36, Willy Tarreau :
> Hi Ilya,
>
> On Mon, May 27, 2019 at 01:40:42AM +0500, ??? wrote:
> > Hello,
> >
> > I added freebsd-11 to cirrus-ci
> >
> > https://cirrus-ci.com/task/5162023978008576
> >
> > should we fix it before 2.0 release ?
>
> As I mentioned on the gi
ср, 29 мая 2019 г. в 15:25, Dmitry Sivachenko :
>
>
> > On 26 May 2019, at 23:40, Илья Шипицин wrote:
> >
> > Hello,
> >
> > I added freebsd-11 to cirrus-ci
> >
> > https://cirrus-ci.com/task/5162023978008576
> >
> > should we fix it
Hello, Gil Bahat!
can you help with troubleshooting?
I created some basic cygwin CI:
https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L25-L30
it fails with
src/ev_poll.c:16:10: fatal error: poll.h: No such file or directory
#include
^~~~
compilation terminated.
mak
I forgot to notice - haproxy is very close to 2.0 release (about 2 weeks or
so).
we wish to be sure it works on cygwin before 2.0 released
пн, 3 июн. 2019 г. в 13:57, Илья Шипицин :
> Hello, Gil Bahat!
>
> can you help with troubleshooting?
>
> I created some basic cygwi
пн, 3 июн. 2019 г. в 17:56, Willy Tarreau :
> Hi Ilya,
>
> On Mon, Jun 03, 2019 at 01:57:48PM +0500, ??? wrote:
> > Hello, Gil Bahat!
> >
> > can you help with troubleshooting?
> >
> > I created some basic cygwin CI:
> >
> > https://github.com/chipitsine/haproxy/blob/master/.travis.yml#L2
пн, 3 июн. 2019 г. в 16:56, Willy Tarreau :
> Hi Aleks,
>
> On Mon, Jun 03, 2019 at 01:42:45PM +0200, Aleksandar Lazic wrote:
> > Is this test usefull in docker setup?
> >
> > ## Starting vtest ##
> > Testing with haproxy version: 2.0-dev5
> > #t
L165-L172
> Regards,
>
> Gil
>
> On Mon, Jun 3, 2019 at 5:53 PM Илья Шипицин wrote:
>
>>
>>
>> пн, 3 июн. 2019 г. в 17:56, Willy Tarreau :
>>
>>> Hi Ilya,
>>>
>>> On Mon, Jun 03, 2019 at 01:57:48PM +0500, ??? wrote:
>&g
Hello,
I'm trying yo build haproxy (git master) on cygwin.
$ make CC=gcc V=1 TARGET=cygwin FLAGS=
...
src/mux_h2.o: In function `h2s_frt_make_resp_data':
/home/chipitsine/haproxy/src/mux_h2.c:4405: undefined reference to `trace'
/home/chipitsine/haproxy/src/mux_h2.c:4405:(.text+0xce79): reloca
), so something must be missing in your build environment.
> Most system headers should be in /usr/include if cygwin-devel is installed,
> so you might want to start with checking if expected header files are there…
>
"something must be missing in your build environment" ... travis-c
T_SYMBOL = --export-all-symbols
>
> endif
>
>
>
> # set the default settings according to the target above
>
>
>
> Other than these two rather small issues 2.0-dev5 built successfully on my
> Cygwin (and I then also successfully built it with threading support, PCRE,
e" resolved that
>
> cpp -v /dev/null -o /dev/null
>
>
>
> This should print the search path – we can then verify that /usr/include
> and other dirs are in it.
>
>
>
> Bob
>
>
>
> *From:* Илья Шипицин
> *Sent:* Monday, June 3, 2019 4:09 PM
>
вт, 4 июн. 2019 г. в 19:05, Willy Tarreau :
> Hi Ilya,
>
> On Tue, Jun 04, 2019 at 12:52:50AM +0500, ??? wrote:
> > src/mux_h2.o: In function `h2s_frt_make_resp_data':
> > /home/chipitsine/haproxy/src/mux_h2.c:4405: undefined reference to
> `trace'
> > /home/chipitsine/haproxy/src/mux_h2.
update LibreSSL to 2.9.2
speed up build by using "make -j3"
cache BoringSSL checkout
build prometeus exporter
add basic cygwin build
add USE_TFO=1, USE_SYSTEMD=1 to linux builds
cheers,
Ilya Shipitsin
From ae71cc45c6db53b0ea4ce4361ecb6e367b75207b Mon Sep 17 00:00:00 2001
F
something went wrong ?
I do not see this commit
ср, 5 июн. 2019 г. в 01:35, Willy Tarreau :
> On Tue, Jun 04, 2019 at 05:04:03PM +0200, Emmanuel Hocdet wrote:
> > Hi,
> >
> > Simple cleanup to limit #defined inflation.
>
> Merged, thanks Manu.
>
> Willy
>
>
Bob,
we have added very basic cygwin CI
https://travis-ci.com/haproxy/haproxy/jobs/205561046
it is "build only". feel free to improve it :)
ср, 5 июн. 2019 г. в 02:49, Zakharychev, Bob :
> Willy,
>
> On Tue, Jun 04, 2019 at 05:52:12PM +, Zakharychev, Bob wrote:
> >> Finally got VTest compi
Ben,
what is the proper way of building 51degree ?
I added "USE_51DEGREES=1 51DEGREES_SRC=contrib/51d/src/pattern" (as I seen
in documentation)
gcc -Iinclude -Iebtree -Wall -Wextra -O2 -fno-strict-aliasing
-Wdeclaration-after-statement -fwrapv -Wno-unused-label
-Wno-sign-compare -Wno-unused-
and running.
>
>
>
> Regards,
>
>
>
> Ben Shillito
> Developer
>
> [image: 51Degrees] <https://51degrees.com/>
>
> O: +44 1183 287152
> E: b...@51degrees.com
> @51Degrees <http://twitter.com/51Degreesmobi>
> 51Degrees <https://www.li
as for popular distro, for example fedora, I'd spent some time on packaging
rpm in fedora copr (rather than telling people proper Makefile options).
if there's an interest in "official" package distro, I'd take part with
fedora copr and maybe few others
ср, 12 июн. 2019 г. в 10:41, Willy Tarreau :
degrees.com/>
>
> O: +44 1183 287152
> E: b...@51degrees.com
> @51Degrees <http://twitter.com/51Degreesmobi>
> 51Degrees <https://www.linkedin.com/company/2171864>
>
> [image: Find out More] <https://51degrees.com/emailsig.aspx>
>
>
>
> *
801 - 900 of 1159 matches
Mail list logo
