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

chore(runtime) readjust cache dir for V8 runtime build #110

Merged
merged 1 commit into from
Jul 14, 2022

Conversation

hishamhm
Copy link
Collaborator

This reconciles the cache directory used by the "Setup cache" step in the ci.yml workflow with the one used by the v8.sh script.

See #109.

This reconciles the cache directory used by the "Setup cache" step
in the ci.yml workflow with the one used by the `v8.sh` script.

See #109.
@codecov
Copy link

codecov bot commented Jul 14, 2022

Codecov Report

Merging #110 (31bbf36) into main (7f20c12) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #110   +/-   ##
=======================================
  Coverage   86.28%   86.28%           
=======================================
  Files          34       34           
  Lines        5426     5426           
=======================================
  Hits         4682     4682           
  Misses        744      744           
Flag Coverage Δ
unit 86.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7f20c12...31bbf36. Read the comment docs.

@thibaultcha thibaultcha merged commit 277e1a5 into main Jul 14, 2022
@thibaultcha thibaultcha deleted the chore/fix-v8-cache branch July 14, 2022 21:58
@hishamhm
Copy link
Collaborator Author

Ah, I should have left this in Draft status! I wanted to re-trigger its CI to make sure that it is caching V8 as expected this time, to make sure it's working before merging. Well, I guess we'll see once main gets a second run!

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.

None yet

2 participants