Stewart X Addison

Xvfb now on (Needed reregistering with SuSE as the correct repositories were not available) It's giving me `No route to host` exceptions on the [extended.system](https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_extended.system_s390x_linux/) test suite

Had issues with `libffi.so.6` not being accessible (possibly after zypper updates afte the Xvfb addition) ... Have symlinked `libffi.so.4` to `libffi.so.6` (as I believe we've done in the past) and...

If I use the `CookieManagerTest` from the JDK11 codebase it passes: ``` jenkins@test-marist-sles12-s390x-1:~/sxa/openjdk-jdk11u> ../jdk8u275-b01.hs/bin/java CookieManagerTest Trying: test-marist-sles12-s390x-1/148.100.86.128 Using: "127.0.0.1" http server listenining on: 46354 ====== CookieManager test 1 ====== Requesting...

Possibly to be superceded by #2329

I'm tempted to switch them all over to `aarch64` instead of `armv8` since I think that name is clearer to most people, and it's consistent with `uname` and what we...

Quick update on this - the Linaro machines are not currently in production, the scaleway ones are going to get decomissioned (and are armv7 not armv8), the packet aarch64 ones...

Still considering keeping armv8 since aarch64 will become ambiguous across armv8, armv8.2 (Required by Dragonwell) and the upcoming armv9

After some discussions with someone at ARM I've come to the conclusion that standardising on `aarch64` is the right approach for the naming, so yes we should go for that...

@Haroon-Khel Is this now complete?

It's Huawei's port and was added via this issue: https://github.com/AdoptOpenJDK/openjdk-build/issues/2420