Dear list!

Author: Martin Tzvetanov Grigorov <mgrigo...@apache.org>
Number of patches: 21

This is an automated relay of the Github pull request:
   Build and test on AARCH64 at GitHub actions

Patch title(s): 
   Add ARM64 testing
   Fix YAML
   Do not use '-it' for 'docker run'
   Create a custom Dockerfile where the build & test will be executed
   Checkout the project
   Checkout VTest and install dependencies in Docker
   Use Ubuntu:20.04 instead of Centos:8
   Extract the Shell script into a file
   Export CC for `make vtest`
   Add dependency to zlib1g-dev
   Add gcc to general dependencies
   Install wget to be able to download OpenSSL
   Disable LeakSanitizer because it fails with:
   Do not build OpenSSL. It is too slow with QEMU
   Remove USE_OPENSSL=0
   Remove testing of WURFL
   Re-enable OpenSSL because without it some tests fail
   Rename arm64.yml to aarch64.yml for consistency
   Use checkout@v2
   Add a README explaining how the testing on AARCH64 works
   Re-enable testing for Windows

Link:
   https://github.com/haproxy/haproxy/pull/617

Edit locally:
   wget https://github.com/haproxy/haproxy/pull/617.patch && vi 617.patch

Apply locally:
   curl https://github.com/haproxy/haproxy/pull/617.patch | git am -

Description:
   Since testing on ARM64/AARCH64 has been [disabled](https://github.com/
   haproxy/haproxy/commit/18b303e9f9b38e3a35b05cfe54d57ce3c81599c0#diff-3
   54f30a63fb0907d4ad57269548329e3) at TravisCI because there were some
   infrastructure related problems I propose a new way to test at GitHub
   Actions.
   The new approach is based on QEMU and uses Docker images
   to simplify the setup of QEMU.
   
   All is nice and shiny but
   there is one big problem - few tests fail consistently:
   
   ```
   ########################## Starting vtest ##########################
   Testing with haproxy version: 2.2-dev0-bbd4d68-993
   #    top  TEST
   reg-tests/ssl/wrong_ctx_storage.vtc FAILED (0.280) exit=2
   #    top
   TEST reg-tests/connection/proxy_protocol_random_fail.vtc FAILED
   (0.306) exit=2
   #    top  TEST reg-tests/seamless-
   reload/abns_socket.vtc FAILED (0.711) exit=2
   #    top  TEST reg-
   tests/http-rules/map_regm_with_backref.vtc FAILED (0.642) exit=2
   #
   top  TEST reg-tests/http-
   rules/converters_ipmask_concat_strcmp_field_word.vtc FAILED (0.778)
   exit=2
   5 tests failed, 0 tests skipped, 48 tests passed
   ########################## Gathering results
   ##########################
   ###### Test case: reg-
   tests/connection/proxy_protocol_random_fail.vtc ######
   ## test
   results in:
   "/tmp/haregtests-2020-05-06_11-59-19.fNnEdV/vtc.7747.3fdec118"
   ---- top  shell_exit not as expected: got 0x007f wanted 0x0000
   ###### Test case: reg-tests/http-
   rules/converters_ipmask_concat_strcmp_field_word.vtc ######
   ##
   test results in:
   "/tmp/haregtests-2020-05-06_11-59-19.fNnEdV/vtc.7747.4f6aaeeb"
   ---- c1   HTTP header is incomplete
   ###### Test case: reg-
   tests/http-rules/map_regm_with_backref.vtc ######
   ## test results
   in: "/tmp/haregtests-2020-05-06_11-59-19.fNnEdV/vtc.7747.2a6adc02"
   ---- c1   HTTP header is incomplete
   ---- s1   HTTP rx failed (fd:6
   read: Connection reset by peer)
   ###### Test case: reg-
   tests/ssl/wrong_ctx_storage.vtc ######
   ## test results in:
   "/tmp/haregtests-2020-05-06_11-59-19.fNnEdV/vtc.7747.6fe1dd3f"
   ---- top  shell_exit not as expected: got 0x007f wanted 0x0000
   ###### Test case: reg-tests/seamless-reload/abns_socket.vtc ######
   ## test results in:
   "/tmp/haregtests-2020-05-06_11-59-19.fNnEdV/vtc.7747.09b9aabe"
   ---- c1   Failed to open 127.0.0.1 39405: (null)
   make: ***
   [Makefile:995: reg-tests] Error 1
   ```
   
   I've explained how
   to run the setup locally in `.github/workflows/aarch64/README.md`.

Instructions:
   This github pull request will be closed automatically; patch should be
   reviewed on the haproxy mailing list (haproxy@formilux.org). Everyone is
   invited to comment, even the patch's author. Please keep the author and
   list CCed in replies. Please note that in absence of any response this
   pull request will be lost.

Reply via email to