-
Notifications
You must be signed in to change notification settings - Fork 110
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
Problem with cache hit permissions (macOS, Linux?) #1087
Comments
Probably it's not only about macOS: |
Unfortunately, I wasn't able to reproduce your example: https://cirrus-ci.com/task/5442098164924416. Here's a full env:
CODECOV_OS: macos
task:
macos_instance:
image: monterey-base
codecov_uploader_cache:
folder: codecov
fingerprint_script:
- curl -Os https://uploader.codecov.io/latest/${CODECOV_OS}/codecov.SHA256SUM
populate_script:
- mkdir -p codecov
- curl -s https://uploader.codecov.io/latest/${CODECOV_OS}/codecov -o codecov/uploader
- chmod +x codecov/uploader
codecov_script: codecov/uploader Or I am missing something here? |
I don't see any valuable difference. The project is open, you can see current complete configuration here: https://github.com/filewatcher/filewatcher/blob/0ad47c5/.cirrus.yaml I've cleared cache today and PR had successful runs: https://cirrus-ci.com/task/6080908112429056 After merge there is the same problem: https://cirrus-ci.com/task/4662261959622656 |
Have you tried clearing caches on |
|
I don't think this is related, but I saw that Cirrus CI is moving from Intel to M1 instances, and Codecov (the problematic executable) doesn't support it yet: codecov/uploader#523 (comment) So, theoretically this issue will be non-relevant sometimes. |
Expected Behavior
Restored from CI cache executable has correct permissions.
After cache reset: https://cirrus-ci.com/build/5438662258196480
Real Behavior
https://cirrus-ci.com/task/6095845136269312?logs=codecov#L0
Related Info
This is a (tick one of the following):
macOS
Test on darwin
codecov_cache
Configuration
The text was updated successfully, but these errors were encountered: