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

Fix wrong CI cache path in the mozilla-central task #426

Merged
merged 1 commit into from
Jan 13, 2021

Conversation

Luni-4
Copy link
Collaborator

@Luni-4 Luni-4 commented Jan 12, 2021

The CI cache for the mozilla-central task probably didn't work because of the wrong CI cache path. This PR fixes this problem.

Thanks in advance for your review! :)

@Luni-4 Luni-4 requested a review from marco-c January 12, 2021 22:37
@codecov-io
Copy link

Codecov Report

Merging #426 (af19774) into master (088011c) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #426   +/-   ##
=======================================
  Coverage   22.18%   22.18%           
=======================================
  Files          45       45           
  Lines        5797     5797           
  Branches      822      822           
=======================================
  Hits         1286     1286           
  Misses       3988     3988           
  Partials      523      523           

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 088011c...af19774. Read the comment docs.

@marco-c marco-c merged commit 309fcfc into mozilla:master Jan 13, 2021
@Luni-4 Luni-4 deleted the fix-mozilla-central-cache branch January 13, 2021 10:49
spacedragon pushed a commit to spacedragon/rust-code-analysis that referenced this pull request Feb 2, 2021
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.

3 participants