btw, I'm going to enable arm64 builds back soon :)
but your efforts are awesome.
ср, 6 мая 2020 г. в 17:18, Martin Grigorov :
> Hi,
>
> I've just created a PR (https://github.com/haproxy/haproxy/pull/617/files)
> that introduces testing on ARM64/AARCH64 at GitHub Actions.
> It almost works!
Hi,
I've just created a PR (https://github.com/haproxy/haproxy/pull/617/files)
that introduces testing on ARM64/AARCH64 at GitHub Actions.
It almost works! There are few tests that fail. Any help finding the reason
is very welcome!
Martin
On Mon, Mar 23, 2020 at 11:12 AM Martin Grigorov
wrote:
Hi Илья,
On Sun, Mar 22, 2020 at 2:46 PM Илья Шипицин wrote:
> Martin,
>
> as the one of the most interested in ARM64 builds, I've got news for you
>
>
> can you try
>
> travis_wait 30 bash -c 'scripts/build-ssl.sh >build-ssl.log 2>&1' || (cat
> build-ssl.log && exit 1)
>
> in travis ? (please
Martin,
as the one of the most interested in ARM64 builds, I've got news for you
can you try
travis_wait 30 bash -c 'scripts/build-ssl.sh >build-ssl.log 2>&1' || (cat
build-ssl.log && exit 1)
in travis ? (please not "travis_wait 30" instead of "travis_wait")
also, it might be important to
well, there are several topics on travis-ci forum related to "output on
ARM64 got truncated in the mid of ..."
Let us disable ARM64 travis-ci builds for few months.
Martin, I'll play with hosted github runner in order to find a way how we
can limit its builds to allowed only.
ср, 18 мар. 2020 г.
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
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
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
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)
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
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
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:
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
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
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
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
ср, 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.
>
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
Hello,
it is not trivial bash redirection misuse fix.
Cheers,
Ilya Shipitcin
From d405c779f1c9e5b37532d0ac95e441a0735899bb Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Tue, 17 Mar 2020 20:57:25 +0500
Subject: [PATCH] CI: proper group output redirection together with travis_wait
19 matches
Mail list logo
