`Java setup process failed due to: Available version not found` should be more specific

[jsoref]

Description:
Java setup process failed due to: Available version not found should specify the requested java version so people don't have to guess

Task version:
main

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:

1. Sync a fork of this repository after the release of a new Severity: high item but before the corresponding PR is merged to this repository

Expected behavior:
Assuming that Java setup process failed due to: Available version not found is problematic, the error should be more specific

Actual behavior:
Java setup process failed due to: Available version not found with no indication of which Java version was requested:

Annotations

9 errors
❌ Basic validation / build (macos-latest)
Process completed with exit code 1.
❌ Basic validation / build (macos-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (macos-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (ubuntu-latest)
Process completed with exit code 1.
❌ Basic validation / build (ubuntu-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (ubuntu-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (windows-latest)
Process completed with exit code 1.
❌ Basic validation / build (windows-latest)
Java setup process failed due to: Available version not found
❌ Basic validation / build (windows-latest)
Java setup process failed due to: Available version not found

---

• Basic validation workflow fails without useful explanation #977 covers the main failure here, this ticket is solely for the fact that Java setup process failed due to: Available version not found isn't terribly helpful

[mahabaleshwars]

Hi @jsoref,
Thank you for creating this issue. We will investigate it and provide feedback as soon as we have some updates.

[chiranjib-swain]

Hi — @jsoref ,

We’ve opened a potential fix in #989 to improve error handling/logging so failures like this show a clearer root cause.

Could you please try it in your repo/workflow and let us know if it resolves the issue (or at least produces more actionable output)? A link to a run would be very helpful — thanks!