duesee / duesee/imap-next

ci: Failed to save cache on windows

Open
#239 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
22
Forks
5
PR merge metrics
No merged PRs in 30d

Description

The windows runner in the CI is the slowest one. Maybe it's related to this error that I saw:

```
Prepare all required actions
Getting action download info
Run ./.github/actions/cache_save
Run actions/cache/save@v4
"C:\Program Files\Git\usr\bin\tar.exe" --posix -cf cache.tzst --exclude cache.tzst -P -C D:/a/imap-next/imap-next --files-from manifest.txt --force-local --use-compress-program "zstd -T0"
Failed to save: Unable to reserve cache with key Windows|test|1, another job may be creating this cache. More details: Cache already exists. Scope: refs/pull/213/merge, Key: Windows|test|1, Version: e83056fabc1136a6df0cebe07959d02e6e5208f662fe3ab3efa0dd5ffb5bbe27
Warning: Cache save failed.
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Inspect .github/actions/cache_save and the Windows CI job, starting with the actions/cache/save@v4 invocation and the logged Windows|test|1 key. Determine why concurrent jobs attempt to reserve the same cache; done means the Windows job saves or skips the cache without the reported reservation failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.