Skip to content

Dual JVM benchmarks are failing #13880

@Akirathan

Description

@Akirathan

For example at https://github.com/enso-org/enso/actions/runs/17310891684/job/49144677438#step:10:5492 :

INFO ide_ci::program::command: sbt ℹ️ [info] Execution finished with an error: java.lang.IndexOutOfBoundsException: Range [40, 40 + 65535) out of bounds for length 4096
   INFO ide_ci::program::command: sbt ℹ️ [info]         at <java> java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:100)
   INFO ide_ci::program::command: sbt ℹ️ [info]         at <java> java.base/jdk.internal.util.Preconditions.outOfBoundsCheckFromIndexSize(Preconditions.java:118)
   INFO ide_ci::program::command: sbt ℹ️ [info]         at <java> java.base/jdk.internal.util.Preconditions.checkFromIndexSize(Preconditions.java:397)
   INFO ide_ci::program::command: sbt ℹ️ [info]         at <java> java.base/java.util.Objects.checkFromIndexSize(Objects.java:417)
   INFO ide_ci::program::command: sbt ℹ️ [info]         at <java> java.base/java.nio.ByteBuffer.get(ByteBuffer.java:913)
  ...

Another failure is in org.enso.benchmarks.generated.Compare_JVM_Modes.Real_Dual_Tests at https://github.com/enso-org/enso/actions/runs/17310891684/job/49144677438#step:10:5657

  INFO ide_ci::program::command: sbt ℹ️ [info] Process: /runner/_work/enso/enso/built-distribution/enso-engine-2025.3.1-dev-linux-amd64/enso-2025.3.1-dev/bin/enso with --run /tmp/temp9615697296109697638.tmp --vm.D=polyglot.enso.classLoading=guest should.be.able.to.get.tables
   INFO ide_ci::program::command: sbt ℹ️ [info] Exit code: 1

... And more problems, like a lot of suspicious logs:

   ...
   INFO ide_ci::program::command: sbt ℹ️ [info] [WARN] [2025-08-29T04:55:47+02:00] [org.enso.librarymanager.local.DefaultLocalLibraryProvider] Candidate library local.Enso_prj13560520769978915109dir at [***/enso_prj13560520769978915109.dir] may not be AOT ready! Use --jvm option when encoutering problems.
   INFO ide_ci::program::command: sbt ℹ️ [info] [WARN] [2025-08-29T04:55:47+02:00] [org.enso.librarymanager.local.DefaultLocalLibraryProvider] Candidate library local.Enso_prj16144645876746290168dir at [***/enso_prj16144645876746290168.dir] may not be AOT ready! Use --jvm option when encoutering problems.
   ...

for example at https://github.com/enso-org/enso/actions/runs/17310891684/job/49144677438#step:10:5937.

Most of these benchmarks seems to fail on Panic "Exit code: 1" throws from

Panic.throw "Exit code: "+code.to_text
. But the whole benchmark suite continues to run and reports some numbers. Note that this means that all the reported numbers for those failing benchmarks are nonsense.

Metadata

Metadata

Labels

--bugType: bug-compilerp-highShould be completed in the next sprint

Type

No type

Projects

Status

🟢 Accepted

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions