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

Add explicit cache-dependency-path to action.yml #102

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tianon
Copy link
Member

@tianon tianon commented Jul 10, 2024

This should squash the Warning: Restore cache failed: Dependencies file is not found in /home/runner/work/xxx/yyy. Supported file pattern: go.sum note we've been getting on all our builds. 🙃

This *should* squash the `Warning: Restore cache failed: Dependencies file is not found in /home/runner/work/xxx/yyy. Supported file pattern: go.sum` note we've been getting on all our builds. 🙃
@tianon tianon requested a review from yosifkit as a code owner July 10, 2024 19:15
@tianon tianon marked this pull request as draft July 10, 2024 19:15
@tianon
Copy link
Member Author

tianon commented Jul 10, 2024

Converting to Draft for now -- we need to test this commit/branch to make sure it actually works before we go ahead with it.

@tianon
Copy link
Member Author

tianon commented Jul 11, 2024

Run tianon/bashbrew@tianon
Run actions/setup-go@v5
  with:
    go-version-file: /home/runner/work/_actions/tianon/bashbrew/tianon/go.mod
    cache-dependency-path: /home/runner/work/_actions/tianon/bashbrew/tianon/go.sum
    check-latest: false
    token: ***
    cache: true
Setup go version spec 1.20
Found in cache @ /opt/hostedtoolcache/go/1.20.14/x64
Added go to the path
Successfully set up Go version 1.20
/opt/hostedtoolcache/go/1.20.14/x64/bin/go env GOMODCACHE
/opt/hostedtoolcache/go/1.20.14/x64/bin/go env GOCACHE
/home/runner/go/pkg/mod
/home/runner/.cache/go-build
Warning: Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.

Nope! 🙃 (although this looks like a new warning, so maybe progress?)

@tianon
Copy link
Member Author

tianon commented Jul 11, 2024

So maybe we should cache: false instead? I don't know what that implies, more research required...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant