In addition to what Martijn said, I think it was me adding the Eclipse OpenJ9-based JVM (the release is called IBM Semeru) to the build matrix. IIRC we had an issue we needed to solve and this is why I added it as a regression test. A normal unit test would not do here.
Since Semeru is the only JVM using OpenJ9, I see that we DO get something from this: Tests across TCK-tested JVMs which are not based on hotspot. One issue I remembered from Apache Shiro: Oracle/Hotspot did include some Encryption aliases which were not defined in the language specification, so OpenJ9 did not implement it. Thus, the default configuration failed when running on Semeru. Am So., 8. Dez. 2024 um 01:31 Uhr schrieb Martijn Verburg <martijnverb...@gmail.com>: > > Semeru is based on OpenJ9 whereas Temurin builds are HotSpot based. It > depends on whether you want to test against the two different JVMs (both > pass the TCK). > > Cheers, > Martijn > > > On Sat, 7 Dec 2024 at 10:13, Elliotte Rusty Harold <elh...@ibiblio.org> > wrote: > > > What's up with Java CI / build (ubuntu-latest, 17, semeru) > > (pull_request)? I just had a PR flake on this due to failure to > > download. Do we get anything from this we don't get from the temurin > > 17 builds? If not, we should remove it. Every additional build we add > > to the CI increases the risk of flakes, even when our tests aren't > > fal;ky at all. > > > > -- > > Elliotte Rusty Harold > > elh...@ibiblio.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
