thank you, I will have a look! ср, 6 мая 2020 г. в 14:27, Martin Grigorov <[email protected]>:
> Hi Илья, > > On Wed, May 6, 2020 at 11:59 AM Илья Шипицин <[email protected]> wrote: > >> do you run tests on GH arm64 agents ? is it dedicated (your own) agents >> attached to your repo ? can you give a link ? >> > > I use Docker + QEMU with GH hosted runner. > You can see the current diff at > https://github.com/haproxy/haproxy/compare/master...martin-g:feature/test-aarch64-on-github-actions > 'windows-latest.yml` is temporary disabled until I'm ready with my > experiments. > > As explained at > https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories > using > self-hosted runner is not secure if they are used for Pull Requests. > They can be used for pushes to `master` branch though since this is > supposed to be a reviewed code! > > But the tests failures I reported below fail on my local machine (x86_64) > and my ARM64 VM. I do not use Docker and/or QEMU here. > > Martin > > >> ср, 6 мая 2020 г. в 13:22, Martin Grigorov <[email protected]>: >> >>> 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 are skipped because >>> they depend on SSL library, e.g.: >>> >>> ... >>> Add test: reg-tests/lua/txn_get_priv.vtc >>> Add test: reg-tests/lua/h_txn_get_priv.vtc >>> Skip reg-tests/ssl/wrong_ctx_storage.vtc because haproxy is not >>> compiled with the required option OPENSSL >>> Skip reg-tests/ssl/ssl_client_auth.vtc because haproxy is not compiled >>> with the required option OPENSSL >>> Skip reg-tests/ssl/add_ssl_crt-list.vtc because haproxy is not >>> compiled with the required option OPENSSL >>> Skip reg-tests/ssl/set_ssl_cert.vtc because haproxy is not compiled >>> with the required option OPENSSL >>> ... >>> >>> but few tests just fail: >>> >>> Testing with haproxy version: 2.2-dev7 >>> # top TEST reg-tests/lua/txn_get_priv.vtc FAILED (5.008) exit=2 >>> # top TEST reg-tests/compression/lua_validation.vtc TIMED OUT (kill >>> -9) >>> # top TEST reg-tests/compression/lua_validation.vtc FAILED (10.009) >>> signal=9 >>> 2 tests failed, 0 tests skipped, 64 tests passed >>> ########################## Gathering results ########################## >>> ###### Test case: reg-tests/compression/lua_validation.vtc ###### >>> ## test results in: >>> "/tmp/haregtests-2020-05-06_09-08-49.WqBiWC/vtc.14212.7fffd08a" >>> ###### Test case: reg-tests/lua/txn_get_priv.vtc ###### >>> ## test results in: >>> "/tmp/haregtests-2020-05-06_09-08-49.WqBiWC/vtc.14212.065f2677" >>> ---- c0 HTTP rx timeout (fd:6 5000 ms) >>> ---- h1 Bad exit status: 0x0100 exit 0x1 signal 0 core 0 >>> Makefile:995: recipe for target 'reg-tests' failed >>> make: *** [reg-tests] Error 1 >>> >>> These tests fail both on AARCH64 and x86_64 consistently until I add >>> back USE_OPENSSL=1 >>> to the flags. >>> >>> Is there an issue with these tests ? >>> >>> 1. >>> https://github.com/haproxy/haproxy/blob/fafa13dd6549ee431f41dc3c1857855974d79bea/.travis.yml#L14 >>> >>> Regards, >>> Martin >>> >>
