The `jvm: true` flag in `package.yaml` is ignored in CLI execution

[JaroslavTulach]

Tested on 2025.2.1-nightly.2025.7.21:

enso$ ENSO_LAUNCHER=native sbt buildEngineDistribution
enso$ ./enso --run test/Generic_JDBC_Tests/
1 tests succeeded.
21 tests failed.
0 tests skipped.
0 groups skipped.

the Generic_JDBC_Tests projects requires execution in JVM mode:

enso$ grep jvm test/Generic_JDBC_Tests/package.yaml 
jvm: true

but it looks like the flag is ignored. Running with explicit --jvm flag works:

enso$ ./enso --jvm --run test/Generic_JDBC_Tests/
22 tests succeeded.
0 tests failed.
0 tests skipped.
0 groups skipped.

[JaroslavTulach]

• probably Allow per-project JVM mode #12529 isn't functioning correctly
• related: Enabled per-project JVM mode configuration #12550 (comment)
• related: Enable NI for engine nightly checks #12531

[JaroslavTulach]

Removing the jvm: true flag is however causing failures of the CI... e.g. the behavior cannot be that bad. Why do I see failures locally, but CI is fine?

Answer

Because CI is using absolute paths, while I am using relative paths and relative paths didn't work right.

[enso-bot]

Jaroslav Tulach reports a new STANDUP for yesterday (2025-07-22):

Progress: .

• jvm: true fix: Fixing jvm: true in package.yaml behavior #13584
• associating classloading with a package: 27dbb11
• assert on wrong dir: Asserting proper CWD #13581
• Package can be null: a7a719a
• planning meeting It should be finished by 2025-07-23.

[enso-bot]

Jaroslav Tulach reports a new STANDUP for yesterday (2025-07-23):

Progress: .

• fixed The jvm: true flag in package.yaml is ignored in CLI execution #13567 by Fixing jvm: true in package.yaml behavior #13584
• fixing Allow -> Column&Any to let any visible type thru #13390 Column & Any by Open type check Type&Any lets all (visible) types thru #13593
• meetings, retro
• demo of Dual JVM mode It should be finished by 2025-07-23.