Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache Not Found for Go 1.24 in GitHub Actions (actions/setup-go@v5) on Ubuntu 24 #562

Open
2 of 5 tasks
mck-prakhar opened this issue Mar 5, 2025 · 1 comment
Open
2 of 5 tasks
Assignees
Labels
bug Something isn't working

Comments

@mck-prakhar
Copy link

mck-prakhar commented Mar 5, 2025

Bug Report: GitHub Actions Cache Not Found for Go 1.24 on Ubuntu 24

Description

The cache is not being restored for Go 1.24 when using actions/setup-go@v5 with caching enabled. The error message indicates that the cache key is not found.

Error Message

Warning: Cache not found for keys: setup-go-Linux-x64-ubuntu24-go-1.24.0-c7d09a7bd10e1d8e9f27bae09890ce6d036d31a3fe281a112bf305abd6dfe560

Action Version

actions/setup-go@v5

Platform

  • Ubuntu 24
  • macOS
  • Windows

Runner Type

  • GitHub-hosted
  • Self-hosted

Tools Version

  • Go version: 1.24

Repo Steps

  1. Define the following step in a GitHub Actions workflow:
    - name: Setup Go
      uses: actions/setup-go@v5
      with:
        go-version: '1.24'
        cache-dependency-path: '**/go.sum'
    
  2. Run the workflow on an Ubuntu 24 Self-hosted runner.
  3. Observe the cache not being found and a warning appearing in the logs.

Expected Behaviour

  • The workflow should successfully restore the cache for Go modules, improving job speed and avoiding redundant downloads.

Actual Behavior

  • The cache is not found, and dependencies must be re-downloaded in every run, negating the benefit of caching.

The issue seems specific to the latest Go version (1.24).

@mck-prakhar mck-prakhar added bug Something isn't working needs triage labels Mar 5, 2025
@priya-kinthali
Copy link

Hello @mck-prakhar👋,
Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.

@mahabaleshwars mahabaleshwars self-assigned this Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants