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

Revert "run coverage on stable rust" #280

Merged
merged 3 commits into from
Sep 10, 2024

Conversation

YeungOnion
Copy link
Contributor

oh dear, I merged the experiment instead of the actual branch.

@YeungOnion YeungOnion merged commit f58cd4c into master Sep 10, 2024
4 checks passed
@YeungOnion YeungOnion deleted the revert-279-ci/coverage-on-stable-rust branch September 10, 2024 01:26
@FreezyLemon
Copy link
Contributor

I mean, it does fix the issue while nightly still has the problem, right?

Copy link

codecov bot commented Sep 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.58%. Comparing base (04ce395) to head (2393f2d).
Report is 9 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #280   +/-   ##
=======================================
  Coverage   93.58%   93.58%           
=======================================
  Files          53       53           
  Lines       11822    11822           
=======================================
  Hits        11064    11064           
  Misses        758      758           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@YeungOnion
Copy link
Contributor Author

Oh you're right.

Pinning a specific date of nightly is probably fine as long as we notice when the nightly works again. I'll add a job step with a timeout so nightly has a chance to succeed and the pinned nightly will provide info.

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.

2 participants