setup-java: Error: getCacheEntry failed: Cache service responded with 503

Description: I am currently attempting to set up the very basic Java workflow for my projects. However, it seems to go wrong somewhere. It has worked with other projects, but the new ones seem to fail. Excuse me if this is totally my fault and something that could easily be resolved. I tried google and nothing seems to turn up.

Task version: Latest, straight from the marketplace.

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Repro steps:
run pipeline with

name: Java CI with Maven

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  build:

    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2
    - name: Set up JDK 16
      uses: actions/setup-java@v2
      with:
        java-version: '16'
        distribution: 'zulu'
        cache: maven
    - name: Build with Maven
      run: mvn -B package --file pom.xml

Expected behavior: Setup Java 😃

Actual behavior:

Extracting Java archive...
/usr/bin/tar xz --warning=no-unknown-keyword -C /home/runner/work/_temp/09a0e8ce-4ea7-45ef-b011-6e29334b9412 -f /home/runner/work/_temp/e47c432c-5e30-4f6e-9d36-b371acaab142
Java 16.0.2+7 was downloaded
Setting Java 16.0.2+7 as the default
Java configuration:
  Distribution: zulu
  Version: 16.0.2+7
  Path: /opt/hostedtoolcache/Java_Zulu_jdk/16.0.2-7/x64
Creating settings.xml with server-id: github
Writing to /home/runner/.m2/settings.xml
Error: getCacheEntry failed: Cache service responded with 503

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 19
  • Comments: 19 (3 by maintainers)

Commits related to this issue

Most upvoted comments

👋 the issue has been mitigated. Thanks for your patience 🙇

Hello, @adrian727

This problem is not caused by setup-java, but by cache issues. I think you can track the progress here and here, as a temporary recommendation to restore functionality, we can suggest disabling caching.

We will keep an eye on the issue and keep this one open in case someone else bumps into the issue until it will be resolved.

Cheers!

i am using actions/setup-java but it looks like the issue is intermittent.

This already happened in the past and the original issue is on the cache action.

Seems like the old issue was also revived by someone and they will most likely look into that! For keeping an eye on it, please follow https://github.com/actions/cache/issues/698#issuecomment-1153555265 or potentially a new issue will be created there!

edit: a new issue was created: https://github.com/actions/cache/issues/820

I got the same issue 😦