New Machine requirement - AIX 7.2TL05 for testing JDK22+

[sxa]

I need to request a new machine:

• New machine operating system (e.g. linux/windows/macos/solaris/aix): AIX 7.2TL05
• New machine architecture (e.g. x64/aarch32/arm32/ppc64/ppc64le/sparc): ppc64
• Provider (leave blank if it does not matter): OSUOSL
• Desired usage: Testing JDK22+ which requires support for OpenXL17 which is only available in a later TL of AIX
• Any unusual specification/setup required:
• How many of them are required: TBC

Please explain what this machine is needed for: Running tests against JDK22+ which is being built with OpenXL17

Follow on to #3208

Three options discussed on the call today:

1. Provision new machines with a suitable level of AIX (Preferred option, and the one we will try first)
2. Upgrade some of the existing test machines to the new level and install the OpenXL17 runtime on them
3. If insufficient capacity is available for (1), decommission some of the existing test machines one at a time and use that capacity to provision replacements.

FYI @suchismith1993

[sxa]

NOTE: Not directly related to getting JDK22+ built and tested but I performed a build of JDK17 using the xlc16 compiler on the new 7.2TL5 build machine and it did not run on the earlier TL that we have on the other machines:

15:47:41  =JAVA VERSION OUTPUT BEGIN=
15:47:41  Error: dl failure on line 542
15:47:41  Error: failed /home/jenkins/workspace/build-scripts/jobs/jdk17u/jdk17u-aix-ppc64-temurin_SmokeTests/jdkbinary/j2sdk-image/lib/server/libjvm.so, because 	0509-022 Cannot load module /home/jenkins/workspace/build-scripts/jobs/jdk17u/jdk17u-aix-ppc64-temurin_SmokeTests/jdkbinary/j2sdk-image/lib/server/libjvm.
15:47:41  	0509-150   Dependent module /usr/jdk-17.0.4+7/../lib/libc++.a(shr2_64.o) could not be loaded.
15:47:41  	0509-152   Member shr2_64.o is not found in archive 
15:47:41  	0509-022 Cannot load module /home/jenkins/workspace/build-scripts/jobs/jdk17u/jdk17u-aix-ppc64-temurin_SmokeTests/jdkbinary/j2sdk-image/lib/server/libjvm.
15:47:41  	0509-150   Dependent module /home/jenkins/workspace/build-scripts/jobs/jdk17u/jdk17u-aix-ppc64-temurin_SmokeTests/jdkbinary/j2sdk-image/lib/server/libjvm could not be loaded.
[Pipeline] }

Ref: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-aix-ppc64-temurin_SmokeTests/240/console
Build was done at https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-aix-ppc64-temurin/390/ 14:24:11 configure: Using xlc C compiler version 16.1.0 [IBM XL C/C++ for AIX, V16.1.0 (5725-C72, 5765-J12) Version: 16.01.0000.0011] so it is seems to be the case (as expected) that if we were to move older versions to build on a TL05 system then we would lose compatibility with earlier TLs that we currently run on, even if we're still using the older compiler.

[aixtools]

which are the systems you are referring to?
In principle - as long as the so-called build-date of the software used to build or compile an executable - it is suppossed to run on systems with a later builddate - the exception would be a lower builddate on a later version of AIX - fictive numbers:

AIX 7.2-TL5-2211 AIX 7.2 TL4-2212 (the build of the TL4 system is one week later, and while it could work - it is not supported because TL4 is behind TL5)

AIX 7.2 TL5-2211 AIX 7.3 TL4-2212 - this combination would be supported - as both oslevel and builddate are higher/later.

Assuming the new AIX 7.2 TL5 system is adopt09 - it's oslevel is:
7200-05-03-2135 - while the earlier systems have builddates of 1810, 1938, and 2028 - all of which are behind.

Looking at AIX 7.2 TL5 - the earliest builddate supported is 2038.

Known Service Packs
-------------------
7200-05-03-2135
7200-05-02-2114
7200-05-02-2113
7200-05-01-2038
7200-05-00-0000

p.s. I suspect the new system is one I am not aware of - as adopt09 was installed in Oct 2023 - not in the last three weeks.

[sxa]

The only "new" system - used for building JDK22 - is indeed adopt09, but it was not fully setup until recently, so that is the machine which is https://ci.adoptium.net/computer/build-osuosl-aix72-ppc64-3/ in jenkins and is used for the building and testing of JDK22+ at the moment e.g.

• https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk22u/job/jdk22u-aix-ppc64-temurin/
• https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk23/job/jdk23-aix-ppc64-temurin/
• https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk/job/jdk-aix-ppc64-temurin/

[sxa]

Looking at the last pipeline, most of the tests have run green but two did not:

• special.functional - several (but not all) AIX targets that have ko_KR, KO_KR, Zh_TW, zh_TW and ZH_TW
• special.openjdk - targets hotspot_custom_0 and 1

Running some experiments in grinder:
JDK22 re-runs:

• special.functional ❌
• special.openjdk ❌
  JDK21 runs from the GA level on the same machine
• special.functional ✅
• special.openjdk ✅
  JDK21 runs from the GA level on an earlier machine
• special.functional ✅
• special.openjdk ✅

Noting that similar failures are occurring no Linux/ppc64le with JDK22 (For special.functional it's some of the _linux_ targets for the zh_TW and ko_KR tests instead of _aix_ - those are referenced in adoptium/aqa-tests#5148 (comment)):

• special.functional
• special.openjdk
  On the basis of the above I think we're good from an AQA perspective for JDK22/AIX.

@smlambert do you agree that we currently no outstanding issues for JDK22/AIX based on the above?

[aixtools]

just to make it easier for me to check installed filesets - is this the new adopt09 system, or a different one. I thought I had all the font requirements setup in the base install image - that everything was cloned from.

However, if some processhas changed symbolic links (part of the problem with two rte - gnu and AIX) - that might be broken.

System name, and I'll research.

[sxa]

just to make it easier for me to check installed filesets - is this the new adopt09 system, or a different one. I thought I had all the font requirements setup in the base install image - that everything was cloned from.

However, if some processhas changed symbolic links (part of the problem with two rte - gnu and AIX) - that might be broken.

System name, and I'll research.

It's adopt09 - the only one we have suitable for building and running JDK22 for now.

But to be clear I'm confident at the moment that this is not a setup issue since the equivalent JDK21 test is fine and we're seeing similar errors on Linux JDK22.

[aixtools]

IBM is currently providing: 7200-05-08-2420 dated June 20, 2024 - which, I expect, is a bit too new as a base level - it leaves practically no room for systems not at the very lastest service pack.

imho: n-3 (7200-05-05), or n-2 (7200-05-06) are better choices.