[PATCH] limit travis-ci to "push" events only, skip pull_requests

2020-03-18 Thread Илья Шипицин
Hello, to reduce build noise, let us skip PR builds cheers, Ilya Shipicin From cb4bc027da998dbc01a9825c891708305d616471 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 18 Mar 2020 21:27:39 +0500 Subject: [PATCH] CI: run travis-ci builds on push only, skip pull requests --- .travis.yml

15 Nonprofit Rules For Slowing COVID-19

2020-03-18 Thread Inside Charity
Fundraising During The Coronavirus Pandemic For starters, let’s agree that panicking and crawling into a hole because of the coronavirus is not a reasonable option. Business goes on, whatever the economic conditions. You can’t not raise funds. You can’t treat loyal and responsive donors like st

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Martin Grigorov
Current master's build passed the problematic point in my TravisCI project: https://travis-ci.org/github/martin-g/haproxy/jobs/663953359 Note: I use TravisCI .org while HAProxy's official project is at .com: https://travis-ci.com/github/haproxy/haproxy I also think this is a problem on TravisCI's e

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Илья Шипицин
I will disable PR builds. On Wed, Mar 18, 2020, 6:27 PM Willy Tarreau wrote: > On Wed, Mar 18, 2020 at 06:21:15PM +0500, ??? wrote: > > let us calm down a bit :) > > Agreed, especially since the build on PRs already happens and already > adds noise. > > > yes, I still believe it is beca

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Martin Grigorov
Hi, On Wed, Mar 18, 2020 at 3:29 PM Willy Tarreau wrote: > On Wed, Mar 18, 2020 at 06:21:15PM +0500, ??? wrote: > > let us calm down a bit :) > > Agreed, especially since the build on PRs already happens and already > adds noise. > > > yes, I still believe it is because of buffering. I

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Willy Tarreau
On Wed, Mar 18, 2020 at 06:21:15PM +0500, ??? wrote: > let us calm down a bit :) Agreed, especially since the build on PRs already happens and already adds noise. > yes, I still believe it is because of buffering. I might have missed > something. > unless I will repair it, I'll drop arm6

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Илья Шипицин
let us calm down a bit :) yes, I still believe it is because of buffering. I might have missed something. unless I will repair it, I'll drop arm64 support on travis (and we will switch to self hosted github action runner)

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Tim Düsterhus
William, Am 18.03.20 um 13:37 schrieb William Lallemand: >> Yes, in fact Travis does this by default. You can check the list of pull >> requests and see the checkmarks or crosses in the list: >> https://github.com/haproxy/haproxy/pulls?q=is%3Apr+is%3Aclosed >> >> GitHub Actions would need to be ex

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread William Lallemand
On Wed, Mar 18, 2020 at 01:32:30PM +0100, Tim Düsterhus wrote: > William, > > Am 18.03.20 um 13:30 schrieb William Lallemand: > > Actually I think it's possible to run the CI on the pull requests :-) > > > > Yes, in fact Travis does this by default. You can check the list of pull > requests and

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Tim Düsterhus
William, Am 18.03.20 um 13:30 schrieb William Lallemand: > Actually I think it's possible to run the CI on the pull requests :-) > Yes, in fact Travis does this by default. You can check the list of pull requests and see the checkmarks or crosses in the list: https://github.com/haproxy/haproxy/p

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread William Lallemand
On Wed, Mar 18, 2020 at 01:23:44PM +0100, William Lallemand wrote: > On Wed, Mar 18, 2020 at 01:17:09PM +0100, Willy Tarreau wrote: > > It's really annoying to have to constantly commits into the project > > just to experiment with random fixes there. The problem could very > > well be in the build

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Tim Düsterhus
Willy, Am 18.03.20 um 13:17 schrieb Willy Tarreau: > That was my first impression as well, but when seeing Ilya's fix I > thought I had incorrectly analysed the situation and that we were > just missing some part of the buffered output. Ilya's fixes are correct, but apply at a later point in time

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread William Lallemand
On Wed, Mar 18, 2020 at 01:17:09PM +0100, Willy Tarreau wrote: > It's really annoying to have to constantly commits into the project > just to experiment with random fixes there. The problem could very > well be in the build-ssl script but it's hard to tell. I was thinking > about disabling this en

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Willy Tarreau
On Wed, Mar 18, 2020 at 01:07:45PM +0100, Tim Düsterhus wrote: > Ilya, > > Am 18.03.20 um 10:27 schrieb ???: > > ??, 18 ???. 2020 ?. ? 13:41, Willy Tarreau : > > > >> On Tue, Mar 17, 2020 at 08:59:46PM +0500, ??? wrote: > >>> Hello, > >>> > >>> it is not trivial bash redirection

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Tim Düsterhus
Ilya, Am 18.03.20 um 10:27 schrieb Илья Шипицин: > ср, 18 мар. 2020 г. в 13:41, Willy Tarreau : > >> On Tue, Mar 17, 2020 at 08:59:46PM +0500, ??? wrote: >>> Hello, >>> >>> it is not trivial bash redirection misuse fix. >> >> Ah cool, thank you Ilya! I was also having a look at it not >>

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Илья Шипицин
ср, 18 мар. 2020 г. в 13:41, Willy Tarreau : > On Tue, Mar 17, 2020 at 08:59:46PM +0500, ??? wrote: > > Hello, > > > > it is not trivial bash redirection misuse fix. > > Ah cool, thank you Ilya! I was also having a look at it not > understanding what was wrong there! Now pushed. > https:

Re: [PATCH] fix errored ARM64 builds in travis-ci

2020-03-18 Thread Willy Tarreau
On Tue, Mar 17, 2020 at 08:59:46PM +0500, ??? wrote: > Hello, > > it is not trivial bash redirection misuse fix. Ah cool, thank you Ilya! I was also having a look at it not understanding what was wrong there! Now pushed. Willy

Re: [PATCH] BUG/MEDIUM: spoe: Use unique engine_id for all agents in all scopes

2020-03-18 Thread Christopher Faulet
Le 18/03/2020 à 04:21, Kevin Zhu a écrit : Hi Christopher Can you please test the config files I attached in this mail, HAProxy version 2.1.3 And you can add some debug code like SPOE_PRINTF in function spoe_init_per_thread to print engin_ids of every agent in every proxy. Then you can see the