-
Notifications
You must be signed in to change notification settings - Fork 15
chore(node_modules): upgrade @actions/cache to v4 and npm update #37
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
chore(node_modules): upgrade @actions/cache to v4 and npm update #37
Conversation
@mlugg i'm having problems with my setup-zig and I think the cache issue is the reason, perhaps this upgrade fixes it? It might be related to #36, but I get
|
This is already done now, thanks! @mrjbq7, that's almost certainly an upstream Zig bug. I'd guess ziglang/zig#23110, which will be solved in the imminent 0.14.1 release. |
It does look like an upstream issue, but it doesn't look like that patch fixes mine.
Using the latest nightly build that should include the patch from ziglang/zig#23645:
Do you have a suggestion how I can investigate this further? |
Trying diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index 31f08b2..b64f099 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -14,4 +14,5 @@ jobs:
- uses: mlugg/setup-zig@v2
with:
version: master
+ use-cache: false
- run: zig build test Or that didn't affect anything? I still see this in the logs
|
Okay! It appears setting diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index 31f08b2..8352903 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -14,4 +14,5 @@ jobs:
- uses: mlugg/setup-zig@v2
with:
version: master
+ cache-size-limit: 1
- run: zig build test It seems to have cleared it, but when I subsequently reverting that change causes it to fail again. I'm not sure how to keep the cache but have it not fail with
|
As mentioned in the @actions/cache npm page