Skip to content

Check-latest is false, but still tries to resolve latest version. Then fails and just passes without setting up the requested version #519

@kalmanbencze

Description

@kalmanbencze

Description:
image
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:
image

Task version:
v3

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

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: false is specified and not fail on "checking latest version" when it still needs to download it.

Actual behavior:
check-latest: false is ignored as seen in screenshot #1, and when a very frequent timeout happens, the acton passes successfully.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions