You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When trying to download java 21 (distribution microsoft) the step failes after some retries, because it aborted without any error message or explanation. This is on a self-hosted runner. We have multiple workflows running at the same time on different self-hosted runners.
Platform:
Ubuntu
macOS
Windows
Runner type:
Hosted
Self-hosted
Repro steps:
run the setup-java action in a self-hosted runner
Expected behavior:
Successful download
Actual behavior:
Action failes and only Error shown is aborted
The text was updated successfully, but these errors were encountered:
We cannot reproduce this issue from our network. Can you please provide further details by adding debug switches to the download task, or perhaps doing a traceroute from the agent prior to downloading (also, does your download agent deal with redirects well?)? Have you tried to do this manually from your own workstation using the same tool the agent does (ie. does the agent download tool deal with 302 redirects)? What happens if you try and download a different version (21.0.3 for instance)?
Just to provide some more context: I've seen the same error twice in the last 2 days, although my workflows run on github hosted default ubuntu runners.
Same error message. Download then again works fine when just re-running the same workflow again.
Description:
When trying to download java 21 (distribution microsoft) the step failes after some retries, because it aborted without any error message or explanation. This is on a self-hosted runner. We have multiple workflows running at the same time on different self-hosted runners.
Platform:
Runner type:
Repro steps:
run the setup-java action in a self-hosted runner
Expected behavior:
Successful download
Actual behavior:
Action failes and only Error shown is aborted
The text was updated successfully, but these errors were encountered: