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 p
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 Travis
On Fri, May 15, 2020 at 11:44:48PM +0500, ??? wrote:
> commit message adjusted
Many thanks for this, Ilya, now pushed!
Willy
commit message adjusted
пт, 15 мая 2020 г. в 22:02, Илья Шипицин :
>
>
> пт, 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
пт, 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 Martin's
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 and
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 at
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, Илья Шипицин :
>
>> probably
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)
>
> https://travis-ci.community/t/undocumented
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 https://githu
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, 202
сб, 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 rea
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
❦ 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 ut
пт, 8 мая 2020 г. в 18:31, Willy Tarreau :
> 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 th
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
> > a
пт, 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 real
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 really annoying to work blindly like this. The
> build model Tra
пт, 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 i
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 is broken by design. Requiring to commit
something for test
пт, 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 t
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 it
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 l
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 u
On Fri, May 08, 2020 at 03:29:26PM +0500, ??? wrote:
> I attached a patch
Pushed, thanks. Next step in 10 minutes :-)
Willy
пт, 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 we'
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.
> > > >
> > >
> > >
пт, 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
> > (e.g.
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
пт, 8 мая 2020 г. в 13:19, Willy Tarreau :
> 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
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 '60
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 builds
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
пт, 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 Ope
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 down
пт, 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 t
пт, 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 somethin
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.
B
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 "
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 glo
пт, 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 builds back.
>>
>> Good idea, just merged now. Let's see how
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.
>
Unfortunately it is not good:
https://t
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
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 du
44 matches
Mail list logo
