gt; napisał:
>
> > 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 no
Value would be more visible if we could react and fix or report builds
issues for j9.
Sylwester
sob., 21 gru 2024, 13:41 użytkownik Benjamin Marwell
napisał:
> In addition to what Martijn said, I think it was me adding the Eclipse
> OpenJ9-based JVM (the release is called IBM Semeru)
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
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
wrote:
> What's up with Java CI / build (ubuntu-latest, 17
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 t