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: Revert github actions coverage until fixed #1290

Merged
merged 1 commit into from Mar 15, 2024

Conversation

TerryHowe
Copy link
Member

What this PR does / why we need it:

It looks like there are problems with v4 coverage I was not aware off. Reverting for now.

codecov/codecov-action#1292

Copy link

codecov bot commented Mar 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.99%. Comparing base (ec23755) to head (5201abc).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1290   +/-   ##
=======================================
  Coverage   81.99%   81.99%           
=======================================
  Files          83       83           
  Lines        4005     4005           
=======================================
  Hits         3284     3284           
  Misses        498      498           
  Partials      223      223           

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

@TerryHowe TerryHowe changed the title Revert github actions coverage until fixed fix: Revert github actions coverage until fixed Mar 15, 2024
@TerryHowe TerryHowe merged commit f1d319f into oras-project:main Mar 15, 2024
8 checks passed
@qweeah
Copy link
Contributor

qweeah commented Mar 16, 2024

Actually, it's not caused by codecov GHA version update, it's a known transient failure on codcov service side. The original PR do passes the build, see logs.

@qweeah
Copy link
Contributor

qweeah commented Mar 16, 2024

Interesting, what I said was not right. It's not a transient failure. Merging the PR will sign the squashed commit with an unkown GPG key, which makes the codecov v4 fail. So even if the PR build passes, the main branch build may still fail.

@TerryHowe
Copy link
Member Author

Interesting. I did create an issue #1291 to update when there is a fix

FeynmanZhou pushed a commit to FeynmanZhou/oras that referenced this pull request May 11, 2024
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

3 participants