Skip to content
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

Error message when a component is requested on GraalVM 21 can be improved #62

Closed
michael-simons opened this issue Sep 20, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@michael-simons
Copy link

When you request a component such as native-image on GraalVM for JDK 21 or higher a misleading error is produced

Run graalvm/setup-graalvm@v1
  with:
    distribution: graalvm-community
    java-version: 21
    components: native-image
    github-token: ***
    set-java-home: true
    check-for-updates: true
    native-image-musl: false
    native-image-job-reports: false
    native-image-pr-reports: false
/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/1d60d5ac-45a7-4113-847b-7fe3662415df -f /home/runner/work/_temp/fe77861f-8945-4f3d-a1e9-79b878b6c46c
Adding graalvm-community-jdk-21.0.0_linux-x64_bin 21.0.0 to tool-cache ...
Error: Unable to locate executable file: gu. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

It complains (rightfully) that gu is not available (Background "Gu is dead", https://medium.com/graalvm/truffle-unchained-13887b77b62c and others), which is an implementation detail here it should be better something along the lines "no need to install this as a component on version x of GraalVM" or similar.

My personal upgrade path was this

image

And I maybe missed warnings on interim distributions and versions.

@fniephaus fniephaus self-assigned this Sep 20, 2023
@fniephaus fniephaus added the bug Something isn't working label Sep 20, 2023
@fniephaus
Copy link
Member

Thanks for raising this! Already working on a fix for this. I just checked and it seems the corresponding test never ran due to a misconfiguration (see 6c7d417).

@michael-simons
Copy link
Author

My pleasure, always happy to give back a bit into that great ecosystem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants