es QEMU -
https://github.com/phpmyadmin/phpmyadmin/blob/c90affe793b56fb6f5e1c7eed676ec9031fb1480/.github/workflows/tests.yml#L51
.
It works but it is much slower than using a real ARM64 machine/VM.
Martin
> пн, 9 авг. 2021 г. в 14:29, Willy Tarreau :
>
>> Hi Martin,
>>
>>
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) -
> https://blog.trav
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
> >
report
> (you can sort by "self" time).
> it would be interesting to compare amd64 <--> arm64
>
> [image: Screenshot from 2020-07-18 13-35-27.png]
>
>
> пт, 10 июл. 2020 г. в 19:00, Martin Grigorov :
>
>> Hello HAProxy community,
>>
>> I wan
).
> it would be interesting to compare amd64 <--> arm64
>
> [image: Screenshot from 2020-07-18 13-35-27.png]
>
>
> пт, 10 июл. 2020 г. в 19:00, Martin Grigorov :
>
>> Hello HAProxy community,
>>
>> I wanted to compare how the newly released HAPro
On Thu, Jul 16, 2020 at 10:22 AM Jerome Magnin wrote:
> Hi Martin,
>
> On Thu, Jul 16, 2020 at 10:05:40AM +0300, Martin Grigorov wrote:
> >
> > I am using such logging configuration (HAProxy built from master branch):
> >
> > global
> > log stdout forma
Hello HAProxy community,
I am using such logging configuration (HAProxy built from master branch):
global
log stdout format raw local0 err
...
defaults
log global
option dontlog-normal
option httplog
option dontlognull
...
But HAProxy still logs entries like the following:
Hello HAProxy community,
I wanted to compare how the newly released HAProxy 2.2 (Congrats!) behaves
under heavy load so I've ran some tests on my x86_64 and aarch64 VMs:
https://medium.com/@martin.grigorov/compare-haproxy-performance-on-x86-64-and-arm64-cpu-architectures-bfd55d1d5566
Without
Hello,
Just FYI: the build is broken since this commit:
https://github.com/haproxy/haproxy/commit/7c18b54106ec21273aea3fe59ba23280e86821f5
https://travis-ci.com/github/haproxy/haproxy/builds
Regards,
Martin
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
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
я Шипицин :
>
>> 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
>
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,
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.
>> > .tr
er because OpenSSL will be used from the cache.
Regards,
Martin
On Fri, May 8, 2020 at 9:18 AM Willy Tarreau wrote:
> 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/hapro
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:
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
d/or QEMU here.
Martin
> ср, 6 мая 2020 г. в 13:22, Martin Grigorov :
>
>> Hello HAProxy team,
>>
>> While working on a PR to build & test HAProxy on AARCH64 at GitHub
>> Actions I've noticed a strange behavior for some of the tests.
>>
>> To reduc
Hello HAProxy team,
While working on a PR to build & test HAProxy on AARCH64 at GitHub Actions
I've noticed a strange behavior for some of the tests.
To reduce the time of the build I've removed USE_OPENSSL=1 from the FLAGS
[1] passed to "make".
The build passed successfully, some of the tests
Hi everyone,
On Mon, Mar 23, 2020 at 11:11 AM Martin Grigorov
wrote:
> Hi Илья,
>
> On Mon, Mar 23, 2020 at 10:52 AM Илья Шипицин
> wrote:
>
>> well, I tried to repro abns failures on x86_64
>> I chose MS Azure VM of completely different size, both number of CPU
ed 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
Hi Илья,
On Mon, Mar 23, 2020 at 10:52 AM Илья Шипицин wrote:
> well, I tried to repro abns failures on x86_64
> I chose MS Azure VM of completely different size, both number of CPU and
> RAM.
> it was never reproduced, say on 1000 execution in loop.
>
> so, I decided "it looks like something
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
Hi,
On Sat, Mar 14, 2020 at 11:26 AM Willy Tarreau wrote:
> Hi Ilya,
>
> On Fri, Jan 24, 2020 at 11:46:45AM +0500, ??? wrote:
> > Hello,
> >
> > let us use clang-9 instead of default clang-7 for linux builds.
>
> It seems I missed this one. Now applied carefully, we'll see. If it
>
Hi David,
On my ARM64 VM `uname -m` returns:
$ uname -m
aarch64
Should your change take 'aarch64' into account as well ?
Martin
On Sun, Mar 15, 2020 at 3:34 PM David CARLIER wrote:
> Oups sorry I really forgot :-)
>
> On Sun, 15 Mar 2020 at 13:32, Martin Grigorov
> wr
Hello,
I've just tested the change on my ARM64 VM and the build is successful!
Regards,
Martin
On Sun, Mar 15, 2020 at 9:12 AM Илья Шипицин wrote:
> Hello,
>
> I added DEBUG_STRICT=1 to all builds.
>
> Ilya Shipitcin
>
Hi
On Sun, Mar 15, 2020 at 3:03 PM Aleksandar Lazic wrote:
> On 15.03.20 11:33, David CARLIER wrote:
> > Hi
> >
> > Here a little patch proposal to fix build on ARM.
> >
> > Regards.
>
> Ähm, maybe my mail client hide the Patch because I can't see it ;-)?
>
It seems David forgot to attach it
Hi Willy,
On Fri, Mar 13, 2020 at 10:03 PM Willy Tarreau wrote:
> Hi Martin,
>
> On Fri, Mar 13, 2020 at 12:35:12PM +0200, Martin Grigorov wrote:
> > Hi ,
> >
> > Suddenly today the build is again green here!
> > I didn't make any changes to my testin
Grigorov
wrote:
>
>
> On Wed, Mar 11, 2020 at 3:06 PM Илья Шипицин wrote:
>
>> I will a look during next weekend
>>
>
> Thank you, Илья!
>
>
>>
>> BTW, I've managed to get Linaro VM :)
>>
>
> Congrats! :-)
>
>
>>
>> On Wed, M
On Wed, Mar 11, 2020 at 3:06 PM Илья Шипицин wrote:
> I will a look during next weekend
>
Thank you, Илья!
>
> BTW, I've managed to get Linaro VM :)
>
Congrats! :-)
>
> On Wed, Mar 11, 2020, 5:40 PM Martin Grigorov
> wrote:
>
>> Hi,
>>
>> On
Hi,
On Mon, Mar 9, 2020 at 10:22 PM Martin Grigorov
wrote:
> Hi,
>
> I am not sure what have changed on my test ARM64 VM but the reg tests
> started timing out.
> Everything is fine on my dev machine (x86_64) and at Travis (
> https://travis-ci.com/haproxy/haproxy).
> I do
Hi Илья,
On Wed, Jan 29, 2020 at 11:34 AM Илья Шипицин wrote:
> Hello,
>
> I started to work on rpm packages.
> I also applied at Linaro for arm64 vm (request is not completed yet).
>
>
> interesting that Lua is not detected:
>
>
>
On Fri, Jan 24, 2020 at 6:43 PM Willy Tarreau wrote:
> On Fri, Jan 24, 2020 at 09:12:58PM +0500, ??? wrote:
> > >> + - make reg-tests VTEST_PROGRAM=../vtest/vtest
> > >> REGTESTS_TYPES=default,bug,devel
> > >>
> > >
> > > let us try that.
>
> OK, now pushed.
>
> > > I will have a look
Thank you, Илья!
On Sun, Jan 19, 2020 at 9:20 AM Илья Шипицин wrote:
> hello,
>
> sometimes arm64 builds fails, I think it is good chance to introduce
> regular builds
> and fix them.
>
> also, few small improvements.
>
> cheers,
> Ilya Shipicin
>
янв. 2020 г. в 09:52, Martin Grigorov :
>
>>
>>
>> On Fri, Jan 17, 2020 at 11:17 PM Martin Grigorov <
>> martin.grigo...@gmail.com> wrote:
>>
>>>
>>>
>>> On Fri, Jan 17, 2020, 23:12 William Lallemand
>>> wrote:
>>>
>
On Fri, Jan 17, 2020 at 11:17 PM Martin Grigorov
wrote:
>
>
> On Fri, Jan 17, 2020, 23:12 William Lallemand
> wrote:
>
>> On Fri, Jan 17, 2020 at 08:50:27PM +0200, Martin Grigorov wrote:
>> > Testing with haproxy version: 2.2-dev0-70c5b0-123
>>
>> This
On Fri, Jan 17, 2020, 23:12 William Lallemand
wrote:
> On Fri, Jan 17, 2020 at 08:50:27PM +0200, Martin Grigorov wrote:
> > Testing with haproxy version: 2.2-dev0-70c5b0-123
>
> This binary was built with code from 1 week ago, it's normal that the test
> does
> not work s
Hi Илья,
On Fri, Jan 17, 2020 at 5:43 PM Илья Шипицин wrote:
>
>
> пт, 17 янв. 2020 г. в 19:33, Martin Grigorov :
>
>>
>>
>> On Fri, Jan 17, 2020 at 4:13 PM Martin Grigorov <
>> martin.grigo...@gmail.com> wrote:
>>
>>> Hi all
Hi William,
On Fri, Jan 17, 2020 at 4:46 PM William Lallemand
wrote:
> On Fri, Jan 17, 2020 at 04:33:22PM +0200, Martin Grigorov wrote:
> >
> > git bisect blaims this commit:
> >
> > 25b569302167e71b32e569a2366027e8e320e80a is the
On Fri, Jan 17, 2020 at 4:13 PM Martin Grigorov
wrote:
> Hi all,
>
> Today's build consistently fails on my ARM64 VM:
>
> ## Starting vtest ##
> Testing with haproxy version: 2.2-dev0-70c5b0-123
> #top TEST reg-tests/mcli
us: 0x0100 exit 0x1 signal 0 core 0
Makefile:964: recipe for target 'reg-tests' failed
make: *** [reg-tests] Error 1
Regards,
Martin
On Fri, Jan 17, 2020 at 9:22 AM Илья Шипицин wrote:
> привет!
>
> пт, 17 янв. 2020 г. в 11:42, Martin Grigorov :
>
>> Привет Илья,
>>
>&g
Привет Илья,
On Thu, Jan 16, 2020 at 10:37 AM Илья Шипицин wrote:
>
>
> чт, 16 янв. 2020 г. в 13:26, Martin Grigorov :
>
>> Hi Илья,
>>
>> On Thu, Jan 16, 2020 at 10:19 AM Илья Шипицин
>> wrote:
>>
>>>
>>> Hello, Martin!
>>&g
istering to this mailing list, so probably the post
from @apache has been moderated. I'll be more careful next time!
Thanks, Илья!
Regards,
Martin
>
> чт, 16 янв. 2020 г. в 12:32, Martin Grigorov :
>
>> Hello HAProxy developers,
>>
>> At work we are going to use more
Hello HAProxy developers,
At work we are going to use more and more ARM64 based servers and HAProxy
is one of the main products we rely on.
So I went checking whether HAProxy project has a CI environment for testing
on ARM architecture.
I've found this recent discussion:
44 matches
Mail list logo