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 Илья Шипицин <[email protected]> wrote: > or we'd better move SSL_LIB, SSL_INC to build-ssl.sh script > > пт, 15 мая 2020 г. в 15:09, Илья Шипицин <[email protected]>: > >> 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 <[email protected]>: >> >>> 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, 2020 at 12:38 PM Илья Шипицин <[email protected]> >>> wrote: >>> >>>> >>>> >>>> сб, 9 мая 2020 г. в 11:45, Willy Tarreau <[email protected]>: >>>> >>>>> 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 Travis uses is broken by design. Requiring to commit >>>>> > > something for testing is utterly wrong. And doing so within the >>>>> > > project that's supposed to being test is further wrong. We already >>>>> > > have 44 patches only on .travis.yml! If this continues like this, >>>>> > > I predict that a "pre-CI" solution will appear to test if your >>>>> > > change is likely to trigger a travis error before it gets merged... >>>>> > >>>>> > You can push changes to a (throwable) branch instead. >>>>> >>>>> Good point, that can also be a solution. But it remains completely >>>>> hackish. It's basically abusing a versioning system to use it as a >>>>> messaging system to indicate "please build with this". >>>>> >>>>> Willy >>>>> >>>> >>>> >>>> I created several topics (no answer yet). >>>> >>>> as for travis-ci rights, it's totally undocumented. but I suspect >>>> travis grants >>>> rights based on github rights. i.e. github admin becomes travis admin >>>> as well. >>>> >>>> https://travis-ci.community/t/arm64-fails-with-non-clear-reason/8529 >>>> >>>> >>>> https://travis-ci.community/t/undocumented-require-admin-permissions/8530 >>>> >>>> >>>> https://travis-ci.community/t/undocumented-operation-requires-create-request-access-to-repository/8528 >>>> >>>> >>>
