-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oracle GraalVM fails on AssertionError: no root node #9477
Comments
Another Oracle GraalVM - only error is reported in #9457 |
I think this line is reason for the |
Another incarnation of the failure. |
Jaroslav Tulach reports a new STANDUP for yesterday (2024-04-01): Progress: - Removing list of hardcoded validGuestTypes: d3c7538
Next Day: Take a look at autoscoped constructors again |
Jaroslav Tulach reports a new STANDUP for yesterday (2024-04-02): Progress: - autoscoped uncached works: 12c8cd5
Next Day: Analyze autoscoped constructors with Dmitry |
Another fix will be provided by 380f5d2 |
Update the GraalVM-related Maven packages from **23.1.2** to **24.0.0**. # Important Notes - Reverted workarounds mentioned in #9477 The language home search functionality in Truffle changed. It used to find the home for Enso from the class loader of `EnsoLanguage`: https://github.com/oracle/graal/blob/graal-23.1.2/truffle/src/com.oracle.truffle.polyglot/src/com/oracle/truffle/polyglot/LanguageCache.java#L362 In 24.0.0, the language home is no longer found via class loader, but via system properties: https://github.com/oracle/graal/blob/graal-24.0.0/truffle/src/com.oracle.truffle.polyglot/src/com/oracle/truffle/polyglot/LanguageCache.java#L353 I provided a "fix" for this by an explicit specification of the `org.graalvm.language.enso.home` system property in our launchers.
This happens when (dry-running) some benchmarks. Locally, this can be reproduced with:
Link to a corresponding failure on the CI: org.enso.benchmarks.generated.Map_Error_Benchmark_Slice_report_warning.Map_Id_All_Errors
The error is:
The text was updated successfully, but these errors were encountered: