Check-latest is false, but still tries to resolve latest version. Then fails and just passes without setting up the requested version #519
Comments
|
upgrading to 3.12.0 may have fixed the issue, I'll close this if it doesn't reproduce anymore. Edit: I upgraded to 3.12.0 and specified 17.0.8+7 as java version but the issue still happens. |
|
Hi, @kalmanbencze 👋 Thanks for the issue, we will take a look! |
kalmanbencze
changed the title
|
Hi, @kalmanbencze 👋 I tried to reproduce the issue, but unfortunately without luck. May I ask you to turn the debug mode on (link to guide how to do this can be found here) and provide us with additional information about the failed runs (links or logs would be appreciated). |
|
Just a gentle ping, @kalmanbencze 📟 |
|
sorry I was afk for a bit, will do and report back. |
|
I had reproduced it with extra logs (I hope): |
|
24_build (featurefamilyrewardsfamilyrewards-implementation).txt |
and others
Description:
We use v3 of the action and use it to set up adopt jdk 17. It's causing a lot of headaches that it's trying to resolve latest version, it times out and just completes without failing. There's other times where it's actually failing:
Task version:
v3
Platform:
Runner type:
Repro steps:
Start a matrix of 40-50 jobs all setting up java with:
- name: Set up JDK 17
uses: actions/setup-java@v3
with:
distribution: 'adopt'
java-version: '17'
cache: 'gradle'
It's guaranteed to happen to at least 5-6 times.
Expected behavior:
It's expected to set up java 17 from cache if
check-latest: falseis specified and not fail on "checking latest version" when it still needs to download it.Actual behavior:
check-latest: falseis ignored as seen in screenshot #1, and when a very frequent timeout happens, the acton passes successfully.The text was updated successfully, but these errors were encountered: