how to perform 2 healthcheck at once ?

Dear Sirs, we are running haproxy for SSL balancing using tcp mode clusters. and we are using http checks. actual config is: listen cluster.auth 0.0.0.0:443 mode tcp option tcpka option httpchk GET /ping.ashx HTTP/1.0 balance source server front-1 x.y.z.t:443 check port 80

how to perform 2 healthcheck at once ?

Dear Sirs, we are running haproxy for SSL balancing using tcp mode clusters. and we are using http checks. actual config is: listen cluster.auth 0.0.0.0:443 mode tcp option tcpka option httpchk GET /ping.ashx HTTP/1.0 balance source server front-1 x.y.z.t:443 check port 80 inter

clang static analysis of haproxy

Hello, I run scan-build (which is clang static analysis tool) on haproxy git source here's result http://chipitsine.github.io/haproxy-1.7-dev/ there some null pointer dereferences and memory leaks, I think worth looking at them. also, is there some bug tracker ? CI (like travis-ci or

Re: clang static analysis of haproxy

hould be freed if args[2] is neither "request" nor "response", > otherwise the allocated address is permanently forgotten. > > > On Mon, Jun 6, 2016 at 12:52 PM, Maciej Katafiasz > <mkatafi...@purestorage.com> wrote: > > On 6 June 2016

Re: clang static analysis of haproxy

2016-10-26 13:26 GMT+05:00 Willy Tarreau : > On Wed, Oct 26, 2016 at 01:15:43PM +0500, ?? wrote: > > as time goes on ... I see, haproxy moved to github ? > > No, it's another fork dedicated to travis that causes some confusion > and that we're trying to smoothly

Re: clang static analysis of haproxy

as time goes on ... I see, haproxy moved to github ? I like github, especially for PR and travis. should I open a PR on those (not very critial) issues ? and what do you think of travis-ci ? I have some experience in using it, very nice. 2016-06-07 15:20 GMT+05:00 Willy Tarreau :

Re: dynamic configuration via DNS SRV records

2016-12-19 5:43 GMT+05:00 jerry : > Hi, > > We use haproxy quite a but at soundhound for fronting our various external > and internal services. We are i the process of moving to a container based > deployment model. With kubernetes in particular, it's as easy as editing 1 >

Re: cppcheck finding

and what about CI ? something like gitlab-ci, travis, jenkins ? I'll invest some efforts in that 2017-09-15 18:04 GMT+05:00 Christopher Faulet <cfau...@haproxy.com>: > Le 15/09/2017 à 08:36, Илья Шипицин a écrit : > >> great, thank for the feedback. >> >

Re: cppcheck finding

2017-09-15 18:22 GMT+05:00 Christopher Faulet <cfau...@haproxy.com>: > Le 15/09/2017 à 15:07, Илья Шипицин a écrit : > >> and what about CI ? >> >> something like gitlab-ci, travis, jenkins ? I'll invest some efforts in >> that >> >> > No CI. T

Re: cppcheck finding

2017-09-15 21:29 GMT+05:00 Aleksandar Lazic : > Hi. > > Willy Tarreau wrote on 15.09.2017: > > > On Fri, Sep 15, 2017 at 06:36:20PM +0500, ??? wrote: > >> I'd say, it's chicken and egg situation. Whichever comes first, tests > or CI. > >> if we start a CI with "just

more cppcheck findings

hello, [contrib/halog/halog.c:1572]: (error) Memory leak: ustat [contrib/mod_defender/defender.c:153]: (error) va_list 'argp' was opened but not closed by va_end(). [contrib/modsecurity/modsec_wrapper.c:109]: (error) va_list 'ap' was opened but not closed by va_end(). [src/51d.c:373]: (error)

Re: cppcheck finding

great, thank for the feedback. there're few things like that [src/flt_http_comp.c:926] -> [src/flt_http_comp.c:926]: (warning) Either the condition 'txn' is redundant or there is possible null pointer dereference: txn. [src/flt_spoe.c:2765] -> [src/flt_spoe.c:2766]: (warning) Either the

Re: more cppcheck findings

hello, in case someone is interested, the full list of cppcheck findings git clone http://git.haproxy.org/git/haproxy.git/ cd haproxy script cppcheck --force --enable=all . Ctrl-D grep '(error' typescript grep '(warning' typescript grep '(style' typescript | grep 'The function ' | grep ' is

cppcheck finding

hello, [src/flt_http_comp.c:926] -> [src/flt_http_comp.c:926]: (warning) Either the condition 'txn' is redundant or there is possible null pointer dereference: txn. should there be && instead of || ? Cheers, Ilya Shipitsin

resolve memory leak in contrib/halog/halog.c

Hello, [contrib/halog/halog.c:1572]: (error) Memory leak: ustat From e58f1f8989715b2fa0c47c9169985d665c32c487 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Fri, 22 Sep 2017 22:33:16 +0500 Subject: [PATCH] BUG/MINOR: contrib/halog: fixing small memory leak Issue was

Re: patch: allow to use any compiler

2017-10-05 1:01 GMT+05:00 Vincent Bernat <ber...@luffy.cx>: > ❦ 4 octobre 2017 23:49 +0500, Илья Шипицин <chipits...@gmail.com> : > > > while some Makefiles allow to use CC, other just stick to gcc. > > I think we should change to > > > > CC ?= gcc >

Re: another cppcheck finding

2017-10-04 14:00 GMT+05:00 Christopher Faulet <cfau...@haproxy.com>: > Le 04/10/2017 à 07:49, Илья Шипицин a écrit : > >> >> >> 2017-10-04 9:15 GMT+05:00 Willy Tarreau <w...@1wt.eu <mailto:w...@1wt.eu>>: >> >> Hi Ilya, >> >>

Re: another cppcheck finding

2017-10-04 9:15 GMT+05:00 Willy Tarreau : > Hi Ilya, > > [also CCing Baptiste] > > On Tue, Oct 03, 2017 at 05:25:17PM +0500, ??? wrote: > > [src/dns.c:2502]: (error) Memory leak: buffer > > > > > > I do not see any "buffer" usage except conditional free. > > should we just

Re: resolve memory leak in contrib/halog/halog.c

Ack/Nack ? 22 сент. 2017 г. 22:44 пользователь "Илья Шипицин" <chipits...@gmail.com> написал: > Hello, > > > [contrib/halog/halog.c:1572]: (error) Memory leak: ustat >

Re: Experimental / broken HTTP/2 support

2017-10-15 23:43 GMT+05:00 Willy Tarreau : > On Sun, Oct 15, 2017 at 07:16:51PM +0100, Aaron West wrote: > > Hi Willy, > > > > Sorry to bother you, just a quick question if I may. > > > > Does support for QUIC imply we'd have rudimentary UDP support as well > > or is it only going to

Re: Haproxy segfault error 4 in libc-2.24

you can try to attach like that https://stackoverflow.com/questions/2152582/start-gdb-using-a-pid (I still think, that core dump is better if possible) 2017-10-02 21:59 GMT+05:00 Marcus Ulbrich : > no chance... error or killing haproxy there is no core file

another cppcheck finding

hello! [src/dns.c:2502]: (error) Memory leak: buffer I do not see any "buffer" usage except conditional free. should we just remove "buffer" from there ? Cheers, Ilya Shipitsin

Re: patch: allow to use any compiler

2017-10-08 15:59 GMT+05:00 Vincent Bernat <ber...@luffy.cx>: > ❦ 8 octobre 2017 15:46 +0500, Илья Шипицин <chipits...@gmail.com> : > > >> > while some Makefiles allow to use CC, other just stick to gcc. > >> > I think we should change to > >&g

Re: patch: allow to use any compiler

2017-10-09 10:10 GMT+05:00 Vincent Bernat <ber...@luffy.cx>: > ❦ 9 octobre 2017 08:49 +0500, Илья Шипицин <chipits...@gmail.com> : > > >> > any particular reason for mixing "CC=gcc" with "CC?=gcc" ? > >> > &g

patch: allow to use any compiler

Hello, while some Makefiles allow to use CC, other just stick to gcc. I think we should change to CC ?= gcc everywhere Cheers, Ilya Shipitsin From 246341f636d085a4e99bdc9f66b5fa3c7bb2b7d3 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 4 Oct 2017 23:43:05 +0500

Re: patch: allow to use any compiler

2017-10-05 1:01 GMT+05:00 Vincent Bernat <ber...@luffy.cx>: > ❦ 4 octobre 2017 23:49 +0500, Илья Шипицин <chipits...@gmail.com> : > > > while some Makefiles allow to use CC, other just stick to gcc. > > I think we should change to > > > > CC ?= gcc >

Re: CI/CD HAProxy

2017-09-16 20:01 GMT+05:00 Aleksandar Lazic : > Hi Olivie. > > Olivier Doucet wrote on 15.09.2017: > > > Hi, > > > > I wanted to open a new thread, as "cppcheck finding" was hijacked with > this CICD / testing ;) > > +1 > > > I think the best is the enemy of the good : why not

Re: Re[2]: CI/CD HAProxy

2017-12-15 13:07 GMT+05:00 Aleksandar Lazic <al-hapr...@none.at>: > Hi > > -- Originalnachricht -- > Von: "Илья Шипицин" <chipits...@gmail.com> > An: "Aleksandar Lazic" <al-hapr...@none.at> > Cc: "Olivier Doucet" <

Re: HAProxy LB causes server to poll for request data for a long time

Try proxy_buffering off; proxy_request_buffering off; in nginx On Nov 15, 2017 8:01 PM, "omer kirkagaclioglu" wrote: Hi, I just put a service that has around 400 - 4K http / https mixed requests per second behind haproxy. The endpoint with the highest rate of requests

how to run vtc files?

hi [ilia@localhost haproxy]$ HAPROXY_PROGRAM=./haproxy varnishtest reg-tests/ssl/h0.vtc top 0.0 extmacro def pwd=/home/ilia/xxx/haproxy top 0.0 extmacro def localhost=127.0.0.1 top 0.0 extmacro def bad_backend=127.0.0.1 36769 top 0.0 extmacro def

Re: centos packages built

Did you try fedora copr? On Dec 26, 2017 9:50 PM, "Angelo Hongens" wrote: > > FYI, I built haproxy packages for centos6 and centos7, and intend to keep > the repo up to date. I run haproxy on dozens of machines, and I manage them > using spacewalk. So I want recent RPM's ;)

Re: [PR] avoid overriding external prefix

2018-01-04 2:13 GMT+05:00 Willy Tarreau : > Hi Stephen, > > On Wed, Jan 03, 2018 at 08:33:14PM +0100, PR Bot wrote: > > Dear list! > > > > Author: Stephen > > Number of patches: 1 > > > > This is an automated relay of the Github pull request: >

Re: patch for enabling gitlab-ci

No interest? On Fri, Jul 13, 2018, 2:58 PM Илья Шипицин wrote: > Hello, > > I created a patch which will allow anyone to build CI > using "CI for external repo" + mirroring on https://gitlab.com > > Cheers, > Ilya Shipitsin >

haproxy tests with sanitizers: bug found ? https://gitlab.com/chipitsine/haproxy/-/jobs/80667862

Hello, I had an idea, what if we will run reg-tests with various sanitizers ? for example, https://gitlab.com/chipitsine/haproxy/-/jobs/80667862 (gcc + sanitize-address). can someone confirm a bug there ? "AddressSanitizer: heap-use-after-free on" I'll add more sanitizers later. thanks for

Re: haproxy tests with sanitizers: bug found ? https://gitlab.com/chipitsine/haproxy/-/jobs/80667862

just for the record, asan was very easy to enable: https://gitlab.com/chipitsine/haproxy/blob/master/.gitlab-ci.yml вт, 10 июл. 2018 г. в 16:35, Илья Шипицин : > Hello, > > I had an idea, what if we will run reg-tests with various sanitizers ? > > for example, > > https://

how to run reg-tests ?

HI, I cloned haproxy. built it using: make TARGET=generic USE_OPENSSL=1 when I run tests, it fails: [root@pf0sqjlx haproxy]# VARNISHTEST_PROGRAM=`which varnishtest` HAPROXY_PROGRAM=`pwd`/haproxy make reg-tests top 0.0 extmacro def pwd=/home/ilia/xxx/haproxy top 0.0 extmacro def

Re: how to run reg-tests ?

I use Fedora 28 if that matters. varnishtest installed from repo (dnf install varnish), it is varnish-5.2.1-4.fc28.x86_64 вт, 10 июл. 2018 г. в 14:58, Илья Шипицин : > HI, > > I cloned haproxy. > built it using: > > make TARGET=generic USE_OPENSSL=1 > > when I run te

Re: how to run reg-tests ?

nice :) вт, 10 июл. 2018 г. в 15:15, Frederic Lecaille : > Hi, > > > On 07/10/2018 12:02 PM, Илья Шипицин wrote: > > I use Fedora 28 if that matters. > > varnishtest installed from repo (dnf install varnish), it is > > varnish-5.2.1-4.fc28.x86_64 > > >

Re: how to run reg-tests ?

yahoo! green tests https://gitlab.com/chipitsine/haproxy/-/jobs/80660454 вт, 10 июл. 2018 г. в 15:15, Frederic Lecaille : > Hi, > > > On 07/10/2018 12:02 PM, Илья Шипицин wrote: > > I use Fedora 28 if that matters. > > varnishtest installed from repo (dnf install var

Re: haproxy tests with sanitizers: bug found ? https://gitlab.com/chipitsine/haproxy/-/jobs/80667862

Thanks, I'll check it out. ср, 11 июл. 2018 г. в 18:20, Frederic Lecaille : > On 07/11/2018 10:41 AM, Frederic Lecaille wrote: > > On 07/10/2018 01:35 PM, Илья Шипицин wrote: > >> Hello, > > > > Hello Ilya, > > > >> I had an idea, what if

how h1_frt_addr is defined during reg tests?

Hello, I'm playing with reg tests. Sometimes they fail for weird reasons. (for example, fedora 28 on gitlab ci) https://gitlab.com/chipitsine/haproxy/-/jobs/81106855 curl -i -k https://${h1_frt_addr}:${h1_frt_port} became curl -i -k https://::1:38627 which is not correct. but I could not

patch for enabling gitlab-ci

Hello, I created a patch which will allow anyone to build CI using "CI for external repo" + mirroring on https://gitlab.com Cheers, Ilya Shipitsin commit c75028307a55636f5530671bfcd936162059beed Author: Ilya Shipitsin Date: Fri Jul 13 14:36:55 2018 +0500 FEATURE: gitlab-ci enabled reg

Re: [PATCH] REGTEST/MINOR: Wrong URI syntax.

sorry, I did not test it on centos 7 https://gitlab.com/chipitsine/haproxy/-/jobs/81501288 (I could not find out what's that, error message is strange, I'll try to investigate on separate vm) чт, 12 июл. 2018 г. в 14:08, Frederic Lecaille : > This is a patch to fix the issue reported by Ilya

Re: [PATCH] REGTEST/MINOR: Wrong URI syntax.

пт, 13 июл. 2018 г. в 13:08, Frederic Lecaille : > On 07/13/2018 09:53 AM, Илья Шипицин wrote: > > sorry, I did not test it on centos 7 > > > > https://gitlab.com/chipitsine/haproxy/-/jobs/81501288 > > > > > > (I could not find out what's t

Re: how h1_frt_addr is defined during reg tests?

yes, it fixed build: https://gitlab.com/chipitsine/haproxy/-/jobs/81225803 чт, 12 июл. 2018 г. в 13:28, Frederic Lecaille : > On 07/11/2018 09:12 PM, Илья Шипицин wrote: > > Hello, > > > > I'm playing with reg tests. Sometimes they fail for weird reasons. > > (for e

haproxy ci (again), gitlab.com ?

hello, I have the following suggestion 1) I will add .gitlab-ci.yml to the haproxy repo (it will include "centos 7" and "fedora 28" builds, just to cover openssl-1.0.2 and openssl-1.1.0) 2) that .gitlab-ci.yml will run reg tests 3) anyone can follow to https://gitlab.com --> new --> CI for

Re: cppcheck finding

any action on that ? 2018-03-08 22:29 GMT+05:00 Olivier Houchard : > Hi, > > On Thu, Mar 08, 2018 at 05:44:31PM +0100, Willy Tarreau wrote: > > Hi, > > > > On Wed, Mar 07, 2018 at 03:26:25PM +0500, ??? wrote: > > > Hello, > > > > > > [src/proto_uxst.c:160]:

cppcheck finding

Hi, [src/51d.c:373]: (error) Invalid number of character '{' when no macros are defined. ?

small cleanup of src/dns.c

Hello, small issue (no real impact) identified by cppcheck From 733d99f42d93898232bb8c3c953b662ee889c034 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Thu, 15 Mar 2018 16:38:38 +0500 Subject: [PATCH] CLEANUP: remove duplicate code in src/dns.c issue was identified by

cppcheck finding

Hello, [src/proto_uxst.c:160]: (warning) Redundant assignment of 'xfer_sock->next->prev' to itself. is it in purpose ?

format warning cleanup (patch attached)

Hello, please review the attached patch Ilya Shipitsin From a7f2e5a064c40a5842decc7e053a6e4a4291df33 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Fri, 6 Apr 2018 17:06:10 +0500 Subject: [PATCH] MINOR: format warnings cleanup issue detected by cppcheck

Re: format warning cleanup (patch attached)

well, I was not sure whether to split into several files or not. ok, will split next time :) 2018-04-06 17:32 GMT+05:00 Willy Tarreau : > Hi Ilya, > > On Fri, Apr 06, 2018 at 05:08:20PM +0500, ??? wrote: > > Hello, > > > > please review the attached patch > > thank you,

Re: Haproxy 1.8.4 crashing workers and increased memory usage

can you try thread sanitizer (in real time)? https://github.com/google/sanitizers/wiki#threadsanitizer I'd like to try myself, however, we do not observe bad things in our environment 2018-04-09 13:24 GMT+05:00 Robin Geuze : > Hey Willy, > > So I made a build this morning

patch (cleanup unused labels)

please review the patch attached cheers, Ilya Shipitsin From 4ca8083844bc6fa1f06d3e8b85158dba64372f5c Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Thu, 29 Mar 2018 15:09:05 +0500 Subject: [PATCH] MINOR / CLEANUP: src/h1.c: remove unused labels issue detected by

Re: patch: fix build when USE_THREAD is not defined

in your patch comparision + empty loop will be executed even if USE_THREADS is not defined. not very big performance overhead actually. 2018-03-24 23:02 GMT+05:00 Christopher Faulet <cfau...@haproxy.com>: > Le 24/03/2018 à 13:19, Илья Шипицин a écrit : > >> please rev

Re: patch: fix build when USE_THREAD is not defined

ok, let's use your approach 2018-03-25 16:52 GMT+05:00 Tim Düsterhus <t...@bastelstu.be>: > Илья, > > Am 24.03.2018 um 19:42 schrieb Илья Шипицин: > > in your patch comparision + empty loop will be executed even if > USE_THREADS > > is not defined. > > not ve

strange cppcheck finding

(it's master) is it in purpose ? [src/ssl_sock.c:1553]: (warning) Invalid test for overflow 'msg+rec_len

Re: strange cppcheck finding

"UB" stands for undefined behaviour. that's the reason why cppcheck is unhappy. how do that properly - that's the question :) 2018-03-20 10:48 GMT+05:00 Willy Tarreau : > On Mon, Mar 19, 2018 at 06:55:46PM +0500, ??? wrote: > > (it's master) > > > > is it in purpose ? > > >

cleanup patch submission

please review attached patch From 7f31259bfc6a86a1beae56c612984c1d4c6b7569 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Fri, 23 Mar 2018 17:41:48 +0500 Subject: [PATCH] CLEANUP: map, stream: remove duplicate code in src/map.c, src/stream.c issue was identified by

compilation is broken without USE_THREAD=1

hi, src/queue.o: In function `pendconn_redistribute': /home/ilia/haproxy/src/queue.c:272: undefined reference to `thread_want_sync' src/queue.o: In function `pendconn_grab_from_px': /home/ilia/haproxy/src/queue.c:311: undefined reference to `thread_want_sync' src/queue.o: In function

patch: fix build when USE_THREAD is not defined

please review attached patch From ec9cdfa848d438378919d4f8f2b1cba2a16f3eaa Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Sat, 24 Mar 2018 17:17:32 +0500 Subject: [PATCH] MINOR: fix build when USE_THREAD is not defined src/queue.o: In function `pendconn_redistribute':

Re: patch to avoid null pointer dereference

вт, 2 окт. 2018 г. в 7:06, Willy Tarreau : > Hi Ilya, > > On Sat, Sep 15, 2018 at 12:55:07AM +0500, ??? wrote: > > hi, > > > > please find attached patch > > > > cheers, > > Ilya Shipitsin > > > From 7961bb27597cf529a88da475d3928d6223a88753 Mon Sep 17 00:00:00 2001 > > From: Ilya

Re: Few problems seen in haproxy? (threads, connections).

> 5. dmesg: no messages. > > With the same system and settings, threads gives 18x lesser RPS than > processes, along with > the other 2 issues given in my mail today. > > > On Thu, Oct 4, 2018 at 12:09 PM Илья Шипицин wrote: > >> haproxy config, nginx config >> non de

Re: Few problems seen in haproxy? (threads, connections).

with > haproxy configuration file as given in my first mail. Around 60 > backend servers are configured in haproxy. > > 3. Backend servers are 2 core VM's running nginx and serving > a file called "/128", which is 128 bytes in size. > > Let me know if yo

Re: Few problems seen in haproxy? (threads, connections).

load testing is somewhat good. can you describe an overall setup ? (I want to reproduce and play with it) чт, 4 окт. 2018 г. в 8:16, Krishna Kumar (Engineering) < krishna...@flipkart.com>: > Re-sending in case this mail was missed. To summarise the 3 issues seen: > > 1. Performance drops 18x

patch to avoid null pointer dereference

hi, please find attached patch cheers, Ilya Shipitsin From 7961bb27597cf529a88da475d3928d6223a88753 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Sat, 15 Sep 2018 00:50:05 +0500 Subject: [PATCH] MINOR: src/connection.c: avoid null pointer dereference found by coverity ---

who controls https://github.com/haproxy/haproxy ?

hello, I wish to enable travis-ci, cirrus-ci builds for github repo I do not see any public member there. who does control it ? thanks!

Re: who controls https://github.com/haproxy/haproxy ?

yep, I'm going to play in my own fork as well. I will show something soon пт, 12 апр. 2019 г. в 16:50, Tim Düsterhus : > Ilya, > > Am 12.04.19 um 10:54 schrieb Илья Шипицин: > > I wish to enable travis-ci, cirrus-ci builds for github repo > > I do not see any public memb

[PATCH] FEATURE/MEDIUM: enable travis-ci builds

Hello, let us enable travis-ci on https://github.com/haproxy/haproxy (more builds will be added later) thanks! Ilya Shipitcin From 0eebbedaef858267b637fd0d05751f1e212eae61 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Tue, 16 Apr 2019 23:08:14 +0500 Subject: [PATCH] FEATURE/MEDIUM:

Re: how does ./reg-tests/seamless-reload/b00000.vtc should work ?

red/green build: https://travis-ci.com/chipitsine/haproxy-1/builds/108555034 вт, 16 апр. 2019 г. в 21:16, Willy Tarreau : > On Tue, Apr 16, 2019 at 05:42:41PM +0200, William Lallemand wrote: > > Hi Ilya, > > > > This is a regression due to recent changes in the master-worker. > > I also found a

Re: [PATCH] FEATURE/MEDIUM: enable travis-ci builds

ср, 17 апр. 2019 г. в 07:14, Willy Tarreau : > On Tue, Apr 16, 2019 at 08:31:04PM +0200, Lukas Tribus wrote: > > Hello Ilya , > > > > On Tue, 16 Apr 2019 at 20:18, ??? wrote: > > > > > > Hello, > > > > > > let us enable travis-ci on https://github.com/haproxy/haproxy > > > (more builds

Re: [PATCH] FEATURE/MEDIUM: enable travis-ci builds

ср, 17 апр. 2019 г. в 07:29, Willy Tarreau : > Hi Ilya, > > On Tue, Apr 16, 2019 at 11:17:49PM +0500, ??? wrote: > > +env: > > + global: > > +- USE_THREAD=1 > > +- USE_OPENSSL=1 > > +- USE_PCRE=1 > > +- USE_ZLIB=1 > > +- USE_GETADDRINFO=1 > > It's unclear to me how

running reg-test when haproxy is built without USE_OPENSSL

Hello, when playing with travis-ci build matrix, I see that the following tests fail reg-tests/ssl/* if haproxy is built without ssl. also, I've found that lua tests are guarded with #REQUIRE_OPTIONS=LUA should we guard ssl test in the same way ? thank! Ilya Shipitcin

Re: running reg-test when haproxy is built without USE_OPENSSL

ср, 17 апр. 2019 г. в 12:14, Frederic Lecaille : > On 4/17/19 9:01 AM, Илья Шипицин wrote: > > Hello, > > Hi, > > > when playing with travis-ci build matrix, I see that the following tests > > fail > > > > reg-tests/ssl/* > > > > if hapro

Re: [PATCH] FEATURE/MEDIUM: enable travis-ci builds

btw, we can run lua tests https://travis-ci.com/chipitsine/haproxy-1/builds/108641032 so... how do we want to run lua ? always enabled ? or two builds (with and without lua) ? ср, 17 апр. 2019 г. в 12:43, Илья Шипицин : > I attached v2 patch > > ср, 17 апр. 2019 г. в 12:25, Иль

Re: [PATCH] FEATURE/MEDIUM: enable travis-ci builds

I attached v2 patch ср, 17 апр. 2019 г. в 12:25, Илья Шипицин : > > > ср, 17 апр. 2019 г. в 12:18, Frederic Lecaille : > >> On 4/16/19 8:17 PM, Илья Шипицин wrote: >> > + - make CC=$CC V=1 TARGET=$TARGET >> > + - export PATH=${PATH}:${PWD}/VTest >> &

exclude some reg-tests if no ssl or pcre is enabled

hello, when playing with travis-ci, I've found that ssl, pcre tests are executed even if haproxy is built without such features. thanks! Ilya Shipitcin From 5e786e8bc2a12ad4b53e3fdbfc3464738fd4e6df Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 17 Apr 2019 12:19:56 +0500 Subject:

Re: [PATCH] FEATURE/MEDIUM: enable travis-ci builds

ср, 17 апр. 2019 г. в 12:18, Frederic Lecaille : > On 4/16/19 8:17 PM, Илья Шипицин wrote: > > + - make CC=$CC V=1 TARGET=$TARGET > > + - export PATH=${PATH}:${PWD}/VTest > > + - export VTEST_PROGRAM="VTest/vtest -v" # "VTest/vtest -v" > &g

Re: PATCH: enable cirrus-ci (freebsd builds)

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 ----- > От: Илья Шипици

Re: significantly different address sanitizer findings for "x86_64" and "ppc64le"

пт, 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 > > > >

Re: [ANNOUNCE] haproxy-2.0-dev3

пт, 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: > > >

PATCH: memory leak fix

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:

Re: PATCH: memory leak fix

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

Re: PATCH: memory leak fix

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 > >

upcoming 2.0 release: freebsd-11 seem to be broken ?

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

Re: cygwin compilation error

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

Re: cygwin compilation error

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.

Re: cygwin build error

вт, 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' > >

Re: cygwin compilation error

> 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: >>> >

Re: [ANNOUNCE] haproxy-2.0-dev5

пн, 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 > > #

Re: cygwin compilation error

пн, 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: > > > >

[PATCH] improve travis-ci builds

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

Re: [PATCH] CLEANUP: ssl: remove unneeded defined(OPENSSL_IS_BORINGSSL)

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 > >

Re: cygwin compilation error

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

Re: upcoming 2.0 release: freebsd-11 seem to be broken ?

ср, 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

Re: upcoming 2.0 release: freebsd-11 seem to be broken ?

ср, 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

cygwin build error

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):

Re: cygwin compilation error

port-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, > ZLib, Ope

Re: cygwin compilation error

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 >

Re: cygwin compilation error

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-ci is an ephemer

  1   2   3   4   5   6   7   8   9   10   >