Native enso bundle contains GraalVM, but --jvm cannot find it

[JaroslavTulach]

While testing enso-bundle download as described here I realized that while running tests in native mode works when calling it with --jvm argument, it fails:

$ ./enso/dist/2025.1.1-nightly.2025.2.18/bin/enso --jvm --run /enso/test/Table_Tests
[WARN] [2025-02-18T06:59:58+01:00] [org.enso.runtimeversionmanager.components.GraalVersionManager] Runtime search path `/home/devel/.local/share/enso/runtime` is not a directory
[WARN] [2025-02-18T06:59:58+01:00] [org.enso.runner.JavaFinder] No appropriate JDK found in the distribution runtimes. Trying system-wide JDK.
[WARN] [2025-02-18T06:59:58+01:00] [org.enso.runner.JavaFinder] No JDK found in JAVA_HOME. Trying java on PATH.
[WARN] [2025-02-18T06:59:58+01:00] [org.enso.runner.JavaFinder] No JDK found on PATH. Cannot start the runtime.
Cannot find java executable

that's unfortunate as ensoup (part of the same bundle download) is able to find JVM:

$ ./enso/bin/ensoup run /enso/test/Table_Tests

What's wrong?

• --jvm tries to find Java executable system-wide. #11500

Probably ensoup is using the portable distribution layout while the handling of --jvm switch isn't - maybe ignoring .enso.portable. CCing @radeusgd

[JaroslavTulach]

I had to

$ mv ~/.local/share/enso/ ~/.local/share/enso.bak

to simulate the problem. As the ./bin/enso --jvm properly searches ~/.local/share/enso/ - it just doesn't seem to deal correctly with .enso.portable bundle.

[JaroslavTulach]

Per @Akirathan request here is a test with AppImage. AppImage, dmg and Windows case will be important if we change project-manager to use --jvm flag instead of the current java based solution:

$ ./enso-linux-x86_64-2025.1.1-nightly.2025.2.18.AppImage --appimage-extract
$ ./squashfs-root/resources/enso/dist/2025.1.1-nightly.2025.2.18/bin/enso --jvm --run ~/NetBeansProjects/enso/enso/test/Table_Tests
[WARN] [org.enso.runtimeversionmanager.components.GraalVersionManager] Runtime search path `/home/devel/.local/share/enso/runtime` is not a directory
[WARN] [org.enso.runner.JavaFinder] No appropriate JDK found in the distribution runtimes. Trying system-wide JDK.
[WARN] [org.enso.runner.JavaFinder] No JDK found in JAVA_HOME. Trying java on PATH.
[WARN] [org.enso.runner.JavaFinder] No JDK found on PATH. Cannot start the runtime.
Cannot find java executable

it is also broken. There is:

$ ls -1 squashfs-root/resources/enso/.enso.bundle 
squashfs-root/resources/enso/.enso.bundle

thus probably this case shall work as well. Right @radeusgd? Walk up from bin/enso, locate .enso.bundle and search for GraalVM among its runtimes. @radeusgd do you have any idea why there is .enso.portable once and .enso.bundle in the other case?

[JaroslavTulach]

Please note that the download section for Enso Engine links to the enso-bundle, not enso-engine!

• that's the reason why Native enso bundle contains GraalVM, but --jvm cannot find it #12302 talks about enso-bundle

[enso-bot]

Pavel Marek reports a new STANDUP for yesterday (2025-02-18):

Progress: - Why do we have so many assets in every release?

• https://github.com/orgs/enso-org/discussions/12313
• Fixing the --jvm option in Fix detection of bundled runtime with --jvm option #12318 It should be finished by 2025-02-21.

GitHub

Reducing amount of assets in our releases · enso-org · Discussion #12313

Let's investigate the amount of assets for every release. A link to a recent release is https://github.com/enso-org/enso/releases/tag/untagged-aed0b8c4d7d0b238bf33 For every platform, we have 6 ass...

[enso-bot]

Pavel Marek reports a new STANDUP for today (2025-02-19):

Progress: - Run a single benchmark on the CI:

• Ability to run just a single benchmark on the CI #12324 (comment)
• Next step for benchmark is to integrate Gather all data from benchmarks #10224
  • More specifically only integrate the new format of the data.
• Append different labels based on which API files changed:
  • Different labels for stdlib API checks #12326
  • Creating a simple Rust generator for the new GH workflow. It should be finished by 2025-02-21.