Re: [PATCH] CI: travis-ci: disable arm64 builds

Hi Илья, On Mon, Aug 9, 2021 at 12:45 PM Илья Шипицин wrote: > I'm using arm64 in Oracle Cloud Ampere A1 Compute | Oracle > > Yes! OCI has an ARM64 VM in their free tier! They also provide easy integration with GitHub Actions -

Re: [PATCH] CI: travis-ci: disable arm64 builds

Hi Willy, On Mon, Aug 9, 2021 at 12:29 PM Willy Tarreau wrote: > Hi Martin, > > On Mon, Aug 09, 2021 at 11:04:34AM +0300, Martin Grigorov wrote: > > TravisCI just announced some improvements related to 'arch: arm64' (using > > Equnix Metal machines) - >

Re: [PATCH] CI: travis-ci: disable arm64 builds

I'm using arm64 in Oracle Cloud Ampere A1 Compute | Oracle also, I've found promising approach (using ARM on Github Actions) Bump Bootstrap version from 5.0.2 to 5.1.0 · phpmyadmin/phpmyadmin@c90affe (github.com)

Re: [PATCH] CI: travis-ci: disable arm64 builds

Hi Martin, On Mon, Aug 09, 2021 at 11:04:34AM +0300, Martin Grigorov wrote: > TravisCI just announced some improvements related to 'arch: arm64' (using > Equnix Metal machines) - https://blog.travis-ci.com/2021-08-06-oss-equinix. Thanks for the info! > But I also had some similar problems with

Re: [PATCH] CI: travis-ci: disable arm64 builds

Hi, On Sat, Aug 7, 2021 at 8:31 AM Willy Tarreau wrote: > Hi Ilya, > > On Tue, Aug 03, 2021 at 02:58:40PM +0500, ??? wrote: > > Hello, > > > > it looks like "something on travis-ci side". > > > > CC src/raw_sock.o > > gcc: fatal error: Killed signal terminated program cc1 > >

Re: [PATCH] CI: travis-ci: disable arm64 builds

Hi Ilya, On Tue, Aug 03, 2021 at 02:58:40PM +0500, ??? wrote: > Hello, > > it looks like "something on travis-ci side". > > CC src/raw_sock.o > gcc: fatal error: Killed signal terminated program cc1 > compilation terminated. > > let us disable arm64 for a while. Yes I noticed a

[PATCH] CI: travis-ci: disable arm64 builds

tsin Date: Tue, 3 Aug 2021 14:54:09 +0500 Subject: [PATCH] CI: travis-ci: temporarily disable arm64 builds few recent builds failed with "gcc: fatal error: Killed signal terminated program cc1", let us disable arm64 builds until investigation --- .travis.yml | 8 1 file changed

Re: [PATCH] enable arm64 builds in travis-ci

Hi Willy, On Fri, May 15, 2020 at 6:07 PM Willy Tarreau wrote: > Ilya, > > > also, I'd suggest to purge travis-ci cache (if you are build in your own > > fork). > > some travis related issue might be related when something is took from > > cache (which was not supposed to happen) > > Could you

Re: [PATCH] enable arm64 builds in travis-ci

Thank you for applying the patch! The ARM64 build passed at https://travis-ci.com/github/haproxy/haproxy/jobs/335338296 ! But it passes only for the builds which have 'haproxy-mirror' : https://travis-ci.com/github/haproxy/haproxy/builds I am not sure what exactly "haproxy-mirror" is in the

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 15, 2020 at 11:44:48PM +0500, ??? wrote: > commit message adjusted Many thanks for this, Ilya, now pushed! Willy

Re: [PATCH] enable arm64 builds in travis-ci

his own travis-ci project. > it usually helps to find caveats (for example, you still get files from > cache which is not desireable) > > it's just for pre-checkin test. > > > >> >> Thanks! >> Willy >> > From 98849dc14e08f1c1fb8899145e1ed24118bb1d8b Mon Sep 17 0

Re: [PATCH] enable arm64 builds in travis-ci

пт, 15 мая 2020 г. в 20:07, Willy Tarreau : > Ilya, > > > also, I'd suggest to purge travis-ci cache (if you are build in your own > > fork). > > some travis related issue might be related when something is took from > > cache (which was not supposed to happen) > > Could you please handle

Re: [PATCH] enable arm64 builds in travis-ci

Ilya, > also, I'd suggest to purge travis-ci cache (if you are build in your own > fork). > some travis related issue might be related when something is took from > cache (which was not supposed to happen) Could you please handle Martin's patch, possibly cut it into several pieces if relevant

Re: [PATCH] enable arm64 builds in travis-ci

that should work indeed. also, I'd suggest to purge travis-ci cache (if you are build in your own fork). some travis related issue might be related when something is took from cache (which was not supposed to happen) пт, 15 мая 2020 г. в 15:26, Martin Grigorov : > Those are set to new values

Re: [PATCH] enable arm64 builds in travis-ci

Those are set to new values at https://github.com/haproxy/haproxy/pull/630/files#diff-354f30a63fb0907d4ad57269548329e3R51 On Fri, May 15, 2020 at 1:11 PM Илья Шипицин wrote: > or we'd better move SSL_LIB, SSL_INC to build-ssl.sh script > > пт, 15 мая 2020 г. в 15:09, Илья Шипицин : > >>

Re: [PATCH] enable arm64 builds in travis-ci

or we'd better move SSL_LIB, SSL_INC to build-ssl.sh script пт, 15 мая 2020 г. в 15:09, Илья Шипицин : > probably, you also need to unset SSL_LIB and SSL_INC > > > > btw, I got an answer how to grant travis-ci rights (for triggering build > manually) > >

Re: [PATCH] enable arm64 builds in travis-ci

probably, you also need to unset SSL_LIB and SSL_INC btw, I got an answer how to grant travis-ci rights (for triggering build manually) https://travis-ci.community/t/undocumented-require-admin-permissions/8530 пт, 15 мая 2020 г. в 14:57, Martin Grigorov : > Hi, > > I've created

Re: [PATCH] enable arm64 builds in travis-ci

Hi, I've created https://github.com/haproxy/haproxy/pull/630 With this change the build passed successfully for 5 mins and 7 secs for ARM64. Please let me know if you prefer me to send it as an attached .patch file here. (I haven't used `git format-patch` before :-/). Martin On Mon, May 11,

Re: [PATCH] enable arm64 builds in travis-ci

сб, 9 мая 2020 г. в 11:45, Willy Tarreau : > On Sat, May 09, 2020 at 08:11:27AM +0200, Vincent Bernat wrote: > > ? 8 mai 2020 14:25 +02, Willy Tarreau: > > > > >> > Let's increase the timeout to see if it has a chance to finish, no ? > > >> > > > >> > > >> yes > > > > > > OK now pushed. It's

Re: [PATCH] enable arm64 builds in travis-ci

On Sat, May 09, 2020 at 08:11:27AM +0200, Vincent Bernat wrote: > ? 8 mai 2020 14:25 +02, Willy Tarreau: > > >> > Let's increase the timeout to see if it has a chance to finish, no ? > >> > > >> > >> yes > > > > OK now pushed. It's really annoying to work blindly like this. The > > build model

Re: [PATCH] enable arm64 builds in travis-ci

❦ 8 mai 2020 14:25 +02, Willy Tarreau: >> > Let's increase the timeout to see if it has a chance to finish, no ? >> > >> >> yes > > OK now pushed. It's really annoying to work blindly like this. The > build model Travis uses is broken by design. Requiring to commit > something for testing is

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 06:14:28PM +0500, ??? wrote: > > You can avoid this by making changes to .travis.yml directly in Travis UI. > > At the right-top part of the page there is "More options" menu. Select > > "Trigger build" and in the dialog you can paste "Custom config". Once you > >

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 18:04, Martin Grigorov : > > > On Fri, May 8, 2020 at 3:25 PM Willy Tarreau wrote: > >> On Fri, May 08, 2020 at 05:04:43PM +0500, ??? wrote: >> > > Let's increase the timeout to see if it has a chance to finish, no ? >> > > >> > >> > yes >> >> OK now pushed. It's

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 17:25, Willy Tarreau : > On Fri, May 08, 2020 at 05:04:43PM +0500, ??? wrote: > > > Let's increase the timeout to see if it has a chance to finish, no ? > > > > > > > yes > > OK now pushed. It's really annoying to work blindly like this. The > build model Travis uses

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 16:45, Willy Tarreau : > On Fri, May 08, 2020 at 04:17:18PM +0500, ??? wrote: > > as far as I understand, arm64 is run inside containers. something like > > docker or lxd. > > > > "Processing triggers for dbus (1.12.2-1ubuntu1.1) ..." > > > > > > dbus is not supposed

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 04:17:18PM +0500, ??? wrote: > as far as I understand, arm64 is run inside containers. something like > docker or lxd. > > "Processing triggers for dbus (1.12.2-1ubuntu1.1) ..." > > > dbus is not supposed to be available from container, right ? No idea but if

Re: [PATCH] enable arm64 builds in travis-ci

as far as I understand, arm64 is run inside containers. something like docker or lxd. "Processing triggers for dbus (1.12.2-1ubuntu1.1) ..." dbus is not supposed to be available from container, right ? пт, 8 мая 2020 г. в 16:15, Илья Шипицин : > another travis-ci bug. > UI does not show full

Re: [PATCH] enable arm64 builds in travis-ci

another travis-ci bug. UI does not show full log: https://api.travis-ci.com/v3/job/329873686/log.txt пт, 8 мая 2020 г. в 15:58, Willy Tarreau : > On Fri, May 08, 2020 at 03:29:26PM +0500, ??? wrote: > > I attached a patch > > Pushed, thanks. Next step in 10 minutes :-) > it did not

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 03:29:26PM +0500, ??? wrote: > I attached a patch Pushed, thanks. Next step in 10 minutes :-) Willy

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 15:09, Willy Tarreau : > On Fri, May 08, 2020 at 03:07:51PM +0500, ??? wrote: > > ??, 8 ??? 2020 ?. ? 14:55, Willy Tarreau : > > > > > On Fri, May 08, 2020 at 01:59:57PM +0500, ??? wrote: > > > > > We don't know how long it gets cached so if we increase it

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 03:07:51PM +0500, ??? wrote: > ??, 8 ??? 2020 ?. ? 14:55, Willy Tarreau : > > > On Fri, May 08, 2020 at 01:59:57PM +0500, ??? wrote: > > > > We don't know how long it gets cached so if we increase it we'll have > > to > > > > leave it. > > > > > > > > > >

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 14:55, Willy Tarreau : > On Fri, May 08, 2020 at 01:59:57PM +0500, ??? wrote: > > > We don't know how long it gets cached so if we increase it we'll have > to > > > leave it. > > > > > > > it is cached forever, until cache is purged manually or some cache key > >

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 01:59:57PM +0500, ??? wrote: > > We don't know how long it gets cached so if we increase it we'll have to > > leave it. > > > > it is cached forever, until cache is purged manually or some cache key > (e.g. openssl version) is changed OK, so do you want me to try

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 11:09:50AM +0300, Martin Grigorov wrote: > I still believe the problem is in the time needed to build OpenSSL, not in > apt[-get]. I agree that it's the most likely. > We can increase temporarily the travis_wait to 60 just to cache the build > of 1.1.1f and then remove

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 8, 2020 at 10:54 AM Илья Шипицин wrote: > > > пт, 8 мая 2020 г. в 12:26, Willy Tarreau : > >> On Fri, May 08, 2020 at 09:34:32AM +0300, Martin Grigorov wrote: >> > It must have started failing when you updated the version of OpenSSL. >> > .travis.yml caches ~/opt folder between

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 12:54:14PM +0500, ??? wrote: > > > The build of OpenSSL is wrapped with travis_wait to reduce the writes to > > > stdout but the default time for travis_wait is 20 mins and this is not > > > enough to build OpenSSL. > > > > That's very likely indeed. > > > > > it

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 12:26, Willy Tarreau : > On Fri, May 08, 2020 at 09:34:32AM +0300, Martin Grigorov wrote: > > It must have started failing when you updated the version of OpenSSL. > > .travis.yml caches ~/opt folder between builds. After the update to > 1.1.1f > > the build doesn't see the

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 09:34:32AM +0300, Martin Grigorov wrote: > It must have started failing when you updated the version of OpenSSL. > .travis.yml caches ~/opt folder between builds. After the update to 1.1.1f > the build doesn't see the OpenSSL binaries in the cache anymore and tries > to

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 11:35, Martin Grigorov : > Hi, > > I think I understand why it started failing. > It must have started failing when you updated the version of OpenSSL. > .travis.yml caches ~/opt folder between builds. After the update to 1.1.1f > the build doesn't see the OpenSSL binaries in

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 11:27, Willy Tarreau : > On Fri, May 08, 2020 at 11:12:00AM +0500, ??? wrote: > > btw, in my fork it is green > > https://travis-ci.com/github/chipitsine/haproxy/jobs/329528056 > > Cool, that tends to confirm the issue remains a bit random. There > is actually

Re: [PATCH] enable arm64 builds in travis-ci

Hi, I think I understand why it started failing. It must have started failing when you updated the version of OpenSSL. .travis.yml caches ~/opt folder between builds. After the update to 1.1.1f the build doesn't see the OpenSSL binaries in the cache anymore and tries to download it and build it.

Re: [PATCH] enable arm64 builds in travis-ci

On Fri, May 08, 2020 at 11:12:00AM +0500, ??? wrote: > btw, in my fork it is green > https://travis-ci.com/github/chipitsine/haproxy/jobs/329528056 Cool, that tends to confirm the issue remains a bit random. There is actually something I don't like in the build report, which is that the

Re: [PATCH] enable arm64 builds in travis-ci

Hi Martin, On Fri, May 08, 2020 at 08:56:07AM +0300, Martin Grigorov wrote: > Unfortunately it is not good: > https://travis-ci.com/github/haproxy/haproxy/jobs/329657180 Indeed it's still not fixed on Travis' side. However what Ilya did actually worked, in that the status is not reported as a

Re: [PATCH] enable arm64 builds in travis-ci

пт, 8 мая 2020 г. в 10:56, Martin Grigorov : > Hi all, > > On Thu, May 7, 2020 at 11:56 PM Willy Tarreau wrote: > >> Hi Ilya, >> >> On Thu, May 07, 2020 at 09:19:48PM +0500, ??? wrote: >> > Hello, >> > >> > let us enable arm64 bui

Re: [PATCH] enable arm64 builds in travis-ci

Hi all, On Thu, May 7, 2020 at 11:56 PM Willy Tarreau wrote: > Hi Ilya, > > On Thu, May 07, 2020 at 09:19:48PM +0500, ??? wrote: > > Hello, > > > > let us enable arm64 builds back. > > Good idea, just merged now. Let's see how that ends up now. >

Re: [PATCH] enable arm64 builds in travis-ci

Hi Ilya, On Thu, May 07, 2020 at 09:19:48PM +0500, ??? wrote: > Hello, > > let us enable arm64 builds back. Good idea, just merged now. Let's see how that ends up now. Thanks, Willy

[PATCH] enable arm64 builds in travis-ci

Hello, let us enable arm64 builds back. Cheers, Ilya Shipitcin From 8c68b4494ba37469de86798fd7c492e38a2a8668 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Thu, 7 May 2020 20:57:26 +0500 Subject: [PATCH] CI: travis-ci: enable arm64 builds again travis-ci arm64 were temporarily disabled

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

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

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

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

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

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

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

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_wai

Re: [PATCH] temporarily disable travis-ci arm64 builds

oook. I was about to add link to mailing list discussion and travis community forum. пт, 20 мар. 2020 г. в 15:57, Willy Tarreau : > On Wed, Mar 18, 2020 at 11:58:09PM +0500, ??? wrote: > > Hello, > > > > due to arm64 instability, let us disab

Re: [PATCH] temporarily disable travis-ci arm64 builds

On Wed, Mar 18, 2020 at 11:58:09PM +0500, ??? wrote: > Hello, > > due to arm64 instability, let us disable arm64 builds until this is > resolved. And applied as well, thanks! Willy

Re: [PATCH] temporarily disable travis-ci arm64 builds

On Wed, Mar 18, 2020 at 11:58:09PM +0500, Илья Шипицин wrote: > Hello, > > due to arm64 instability, let us disable arm64 builds until this is > resolved. > > Cheers, > Ilya Shipitcin > From b39b8a6e4ebcae5a28f497170d4ae8e6b208023f Mon Sep 17 00:00:00 2001 > From:

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

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

[PATCH] temporarily disable travis-ci arm64 builds

Hello, due to arm64 instability, let us disable arm64 builds until this is resolved. Cheers, Ilya Shipitcin From b39b8a6e4ebcae5a28f497170d4ae8e6b208023f Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 18 Mar 2020 23:37:12 +0500 Subject: [PATCH] CI: temporarily disable unstable travis

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

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

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

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

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

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

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

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

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

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

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:

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

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

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

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

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

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

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

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

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

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

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

[PATCH] fix errored ARM64 builds in travis-ci

travis_wait is bash function, it was wrongly grouped with output redirection which leads to ARM64 builds errors last week --- .travis.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 5808386e3..c7dbf8d38 100644 --- a/.travis.yml +++ b/.travis.yml

Re: arm64 builds?

On Fri, Jan 24, 2020 at 10:31:14AM +0100, Willy Tarreau wrote: > This is really annoying, so much time spent dealing with bogus warnings > is really irritating. I'm going to work around it with a cast to unsigned > short. > > The worst part of it is that if it emits such a warning, who knows how

Re: arm64 builds?

On Fri, Jan 24, 2020 at 07:12:49AM +0500, ??? wrote: > > it was ubuntu 18.04 + gcc8, I'll try 19.10 + gcc9 > > > > gcc9 produces the same warning OK, I've put my hands on an ubuntu-18.04 + gcc8 32 bits. And now I can confirm it definitely is a gcc bug. The code is the same as a few

Re: arm64 builds?

On Fri, Jan 24, 2020 at 07:12:49AM +0500, ??? wrote: > ??, 24 ???. 2020 ?. ? 01:04, ??? : > > > > > > > ??, 24 ???. 2020 ?. ? 00:54, Willy Tarreau : > > > >> On Fri, Jan 24, 2020 at 12:46:12AM +0500, ??? wrote: > >> > > diff --git a/Makefile b/Makefile > >> > > index

Re: arm64 builds?

пт, 24 янв. 2020 г. в 01:04, Илья Шипицин : > > > пт, 24 янв. 2020 г. в 00:54, Willy Tarreau : > >> On Fri, Jan 24, 2020 at 12:46:12AM +0500, ??? wrote: >> > > diff --git a/Makefile b/Makefile >> > > index 8399f6ca35..4757bc77e6 100644 >> > > --- a/Makefile >> > > +++ b/Makefile >> > >

Re: arm64 builds?

пт, 24 янв. 2020 г. в 00:54, Willy Tarreau : > On Fri, Jan 24, 2020 at 12:46:12AM +0500, ??? wrote: > > > diff --git a/Makefile b/Makefile > > > index 8399f6ca35..4757bc77e6 100644 > > > --- a/Makefile > > > +++ b/Makefile > > > @@ -199,6 +199,7 @@ SPEC_CFLAGS += $(call >

Re: arm64 builds?

On Fri, Jan 24, 2020 at 12:46:12AM +0500, ??? wrote: > > diff --git a/Makefile b/Makefile > > index 8399f6ca35..4757bc77e6 100644 > > --- a/Makefile > > +++ b/Makefile > > @@ -199,6 +199,7 @@ SPEC_CFLAGS += $(call cc-opt,-Wshift-negative-value) > > SPEC_CFLAGS += $(call

Re: arm64 builds?

чт, 23 янв. 2020 г. в 23:17, Willy Tarreau : > On Thu, Jan 23, 2020 at 10:59:00PM +0500, ??? wrote: > > > Could you please try to use (size_t) instead of (unsigned int) ? If > it's > > > enough to shut it up, I'm fine with doing that change. Otherwise we'll > > > probably get rid of that

Re: arm64 builds?

On Thu, Jan 23, 2020 at 07:41:11PM +0100, Tim Düsterhus wrote: > Willy, > > Am 23.01.20 um 19:17 schrieb Willy Tarreau: > > Thanks for the test! So basically this clearly proves we respect the > > calling convention but the compiler still complains. OK I'm seeing in > > the mad that it's for

Re: arm64 builds?

Willy, Am 23.01.20 um 19:17 schrieb Willy Tarreau: > Thanks for the test! So basically this clearly proves we respect the > calling convention but the compiler still complains. OK I'm seeing in > the mad that it's for functions "decorated" with the "alloc_size" > attribute. Thus in short they

Re: arm64 builds?

On Thu, Jan 23, 2020 at 10:59:00PM +0500, ??? wrote: > > Could you please try to use (size_t) instead of (unsigned int) ? If it's > > enough to shut it up, I'm fine with doing that change. Otherwise we'll > > probably get rid of that stupid warning. > > > > CC src/server.o > CC

Re: arm64 builds?

чт, 23 янв. 2020 г. в 15:14, Willy Tarreau : > On Thu, Jan 23, 2020 at 01:09:22PM +0500, ??? wrote: > > hello, > > > > I tried to build using cross compiler (arm32 on amd64). sorry for > > screenshot. > > Willy, do you mean errors like that ? > > So for those not seeing the screenshot,

Re: arm64 builds?

On Thu, Jan 23, 2020 at 03:21:40PM +0500, ??? wrote: > also, can we treat warnings as errors for CI builds ? it would save a bunch > of time, instead of > looking at build log, we can watch for build status. Yes definitely. You just have to add "ERR=1" to your "make" command line and it

Re: arm64 builds?

чт, 23 янв. 2020 г. в 15:14, Willy Tarreau : > On Thu, Jan 23, 2020 at 01:09:22PM +0500, ??? wrote: > > hello, > > > > I tried to build using cross compiler (arm32 on amd64). sorry for > > screenshot. > > Willy, do you mean errors like that ? > > So for those not seeing the screenshot,

Re: arm64 builds?

On Thu, Jan 23, 2020 at 01:09:22PM +0500, ??? wrote: > hello, > > I tried to build using cross compiler (arm32 on amd64). sorry for > screenshot. > Willy, do you mean errors like that ? So for those not seeing the screenshot, it says: warning: argument 1 range [2147483648, 4294967295]

Re: arm64 builds?

hello, I tried to build using cross compiler (arm32 on amd64). sorry for screenshot. Willy, do you mean errors like that ? [image: Screenshot from 2020-01-23 13-03-49.png] ср, 6 нояб. 2019 г. в 12:26, Willy Tarreau : > Hi Ilya, > > On Tue, Nov 05, 2019 at 07:20:43PM +0500, ???

Re: arm64 builds?

Hi Ionel, On Mon, Nov 04, 2019 at 02:10:56PM +0100, GARDAIS Ionel wrote: > FWIW, when I build for armhf (RaspberryPi 3b with Raspbian buster), I have to > add -latomic to the LD_FLAGS. It's not the case for me but I had to add it for another one, I think it was for the mips running in my build

Re: arm64 builds?

Hi Ilya, On Tue, Nov 05, 2019 at 07:20:43PM +0500, ??? wrote: > only arm64 are available. > we can try arm using cross build, for example. Then don't bother with this, it's likely then that they will not have all the environment available. Maybe even their hardware does not support

Re: arm64 builds?

пн, 4 нояб. 2019 г. в 17:49, Willy Tarreau : > Hi Ilya, > > On Mon, Nov 04, 2019 at 12:18:49AM +0500, ??? wrote: > > hello, > > > > should we switch some builds to arm64? > > > > https://blog.travis-ci.com/2019-10-07-multi-cpu-architecture-support > > Ah that's interesting! I frequently

Re: arm64 builds?

Hi, FWIW, when I build for armhf (RaspberryPi 3b with Raspbian buster), I have to add -latomic to the LD_FLAGS. Ionel - Mail original - De: "Willy Tarreau" À: " ???" Cc: "haproxy" Envoyé: Lundi 4 Novembre 2019 13:48:57 Objet: Re: arm64 bui

Re: arm64 builds?

Hi Ilya, On Mon, Nov 04, 2019 at 12:18:49AM +0500, ??? wrote: > hello, > > should we switch some builds to arm64? > > https://blog.travis-ci.com/2019-10-07-multi-cpu-architecture-support Ah that's interesting! I frequently build for arm/arm64 but I agree it would be nice to have this

arm64 builds?

hello, should we switch some builds to arm64? https://blog.travis-ci.com/2019-10-07-multi-cpu-architecture-support thanks, Ilya Shipitsin