On Tue, 27 Oct 2020 06:29:54 GMT, Aleksey Shipilev <[email protected]> wrote:
>>> My rationale is simple: I am playing the whack-a-mole against the ongoing >>> x86_32 regressions here >> >> Would it be possible that we add a Travis hook so that commits get tested >> once before they are merged? >> >> Travis supports all of the important architectures of OpenJDK on Linux these >> days: https://docs.travis-ci.com/user/multi-cpu-architectures/ > >> > My rationale is simple: I am playing the whack-a-mole against the ongoing >> > x86_32 regressions here >> >> Would it be possible that we add a Travis hook so that commits get tested >> once before they are merged? > > Maybe, but that would be beyond the scope of this PR. These GH actions > workflows go the long way already to make pre-integration tests, and they > already run and used by OpenJDK contributors. I see immediate value in > improving GH workflows, and see no clear estimate how much work would be > involved in hooking up Travis, and what the project-wide consequences would > be. If you want, open a new bug, prototype the change, discuss it there, and > see if that is an acceptable thing to do. Let me coop this PR to rename x32 -> x86, among other cosmetic changes. Once #830 lands, I'll update x32 -> x86 in those new blocks as well. This way, we can have best of both worlds: x86_32 would start testing, and we would do the follow-ups here. ------------- PR: https://git.openjdk.java.net/jdk/pull/869
