Initial test of updated workflow with local graalvm artefacts

[jerboaa]

This is an initial set for CI testing the issue of JDK bytecode level
compatibility of graalvm maven artefacts. It uses the new --maven-deploy-local
flag and does the following:

1. Builds Mandrel and also installs maven artefacts to the local repo
2. Archives the maven repo, specifically the org/graalvm artefacts as well as records the maven version being used by the local maven install.
3. Builds quarkus with JDK 11 (currently the lowest supported JDK version) by using pre-installed graalvm artefacts built in step 2. It also sets the graal-sdk version via a property, to the locally available one.
4. Checks whether the build passes (as CI does on it's own) and also verifies no extra org.graalvm artefacts have been downloaded from the Internet when building quarkus.
5. Uses the locally built GraalVM artefacts for Quarkus native IT tests (which will show issues ahead of the GraalVM release; good thing!).

Test actions:

• Successful run: https://github.com/jerboaa/graal/actions/runs/6144976702 and https://github.com/jerboaa/graal/actions/runs/6146546436
• Broken run (sanity check [GR-47084] Change the compliance of com.oracle.svm.core.annotate and org.graalvm.home to JDK11. oracle/graal#6949 is being present in the trees). Expected failure. https://github.com/jerboaa/graal/actions/runs/6146384597/job/16676257542#step:10:5589

Closes: #526

[jerboaa]

Keeping in draft until CI runs complete.

[jerboaa]

One caveat of this update is that now mandrel and quarkus build are being serialized, since the quarkus build depends on the locally deployed maven artefacts from the earlier mandrel build.

[zakkak]

LGTM, I only have a couple of comments/questions.

[jerboaa]

The move to 23.1.x graalvm in native image tests will reveal a different set of problems. For example:

Error: Class-path entry file:///home/runner/work/graal/graal/quarkus/integration-tests/hibernate-orm-panache-kotlin/target/quarkus-integration-test-hibernate-orm-panache-kotlin-999-SNAPSHOT-native-image-source-jar/lib/org.graalvm.sdk.collections-23.1.0.0.SNAPSHOT.jar contains class org.graalvm.collections.EconomicMapWrap. This class is part of the image builder itself (in file:///home/runner/work/graal/graal/graalvm-home/lib/jvmci/collections.jar) and must not be passed via -cp. This can be caused by a fat-jar that illegally includes svm.jar (or graal-sdk.jar) due to its build-time dependency on it. As a workaround, -H:+AllowDeprecatedBuilderClassesOnImageClasspath allows turning this error into a warning. Note that this option is deprecated and will be removed in a future version.
com.oracle.svm.core.util.UserError$UserException: Class-path entry file:///home/runner/work/graal/graal/quarkus/integration-tests/hibernate-orm-panache-kotlin/target/quarkus-integration-test-hibernate-orm-panache-kotlin-999-SNAPSHOT-native-image-source-jar/lib/org.graalvm.sdk.collections-23.1.0.0.SNAPSHOT.jar contains class org.graalvm.collections.EconomicMapWrap. This class is part of the image builder itself (in file:///home/runner/work/graal/graal/graalvm-home/lib/jvmci/collections.jar) and must not be passed via -cp. This can be caused by a fat-jar that illegally includes svm.jar (or graal-sdk.jar) due to its build-time dependency on it. As a workaround, -H:+AllowDeprecatedBuilderClassesOnImageClasspath allows turning this error into a warning. Note that this option is deprecated and will be removed in a future version.
	at org.graalvm.nativeimage.builder/com.oracle.svm.core.util.UserError.abort(UserError.java:73)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageClassLoaderSupport.reportBuilderClassesInApplication(NativeImageClassLoaderSupport.java:907)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.ImageClassLoader.loadAllClasses(ImageClassLoader.java:105)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.buildImage(NativeImageGeneratorRunner.java:385)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.build(NativeImageGeneratorRunner.java:711)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.start(NativeImageGeneratorRunner.java:142)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.main(NativeImageGeneratorRunner.java:97)

See https://github.com/jerboaa/graal/actions/runs/6146546436/job/16682581790#step:12:415

But that's another issue. Moving out of draft. As CI testing seems to be doing what it's supposed to.

[zakkak]

This reminds me of quarkusio/quarkus#28650, we probably just need to expand the exclusion list.

[jerboaa]

This reminds me of quarkusio/quarkus#28650, we probably just need to expand the exclusion list.

+1. Do you mind creating a patch for this, please?

[zakkak]

This reminds me of quarkusio/quarkus#28650, we probably just need to expand the exclusion list.

+1. Do you mind creating a patch for this, please?

Sure, I 'll take care of it tomorrow

[jerboaa]

https://github.com/jerboaa/graal/actions/runs/6146546436/job/16682586135 is the test run with this. The remaining issues are to do with this issue mentioned above and other known Mandrel IT issues tracked elsewhere. I'm going to merge.

[jerboaa]

Unfortunately, that broke the GraalVM Community CI build. Fix in #566

[zakkak]

@jerboaa it also breaks the "gradle tooling" test, see https://github.com/jerboaa/graal/actions/runs/6146546436/job/16682586395#step:12:465

It looks like we need a way to make gradle aware of the local artifacts.

[jerboaa]

@jerboaa it also breaks the "gradle tooling" test, see https://github.com/jerboaa/graal/actions/runs/6146546436/job/16682586395#step:12:465

It looks like we need a way to make gradle aware of the local artifacts.

Thanks, yes I noticed it. I have no idea how to do that. Perhaps it needs to get some property set (-Dgraal.sdk-version=<released-version>) or something?

[jerboaa]

Anyone with more gradle experience than myself can probably fix this easily? I'll look into it later this week.

[zakkak]

I am also not familiar with gradle, but I will take care of it (reaching out to others if necessary). Thanks for your work on this.