-
-
Notifications
You must be signed in to change notification settings - Fork 45
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 LFS Objects in the TARDIS-Carsus Compatibility Check Workflow #327
Cache LFS Objects in the TARDIS-Carsus Compatibility Check Workflow #327
Conversation
change env file path change env file path change path again change path again skip first step path again Package path
Fix atom data path
repo path test
Fix package path
Fix notebook path Fix notebook path Require carsus build to run again before running tardis build
Fix output format of atom data notebook Fix atom data path again Print atom data path Fix atom data path
…the new atomic data file
Fix atomic data path
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Codecov Report
@@ Coverage Diff @@
## master #327 +/- ##
==========================================
- Coverage 74.44% 73.36% -1.09%
==========================================
Files 23 25 +2
Lines 2614 3187 +573
==========================================
+ Hits 1946 2338 +392
- Misses 668 849 +181
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
76bc01b
to
07f4570
Compare
.github/workflows/bridge.yml
Outdated
id: lfs-cache | ||
with: | ||
path: tardis-refdata/.git/lfs | ||
key: ${{ runner.os }}-lfs-${{ hashFiles('tardis-refdata/.lfs-assets-id') }}-v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why v1
is hardcoded?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case we want to invalidate the cache manually- actions/checkout#165
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we use a CACHE_NUMBER: 0
variable on top of the file for that (I think setting to 1 is better though) and then replace v1
with v${{ env.CACHE_NUMBER }}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @epassaro.
Could you rebase this PR to master? |
01d61af
to
07f4570
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
📝 Description
📌 Resources
Examples, notebooks, and links to useful references.
🚦 Testing
How did you test these changes?
☑️ Checklist
build_docs
label