Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@YongGoose
Copy link
Member

  • I have registered the PR changes.

Ⅰ. Describe what this PR did

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

@funky-eyes funky-eyes changed the title hotfix : fix codecov bug bugfix : fix codecov bug May 21, 2025
@funky-eyes funky-eyes changed the title bugfix : fix codecov bug bugfix: fix codecov bug May 21, 2025
Copy link
Member

@jsbxyyx jsbxyyx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@codecov
Copy link

codecov bot commented May 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.94%. Comparing base (f665a79) to head (bf14d74).
Report is 1 commits behind head on 2.x.

Additional details and impacted files
@@             Coverage Diff              @@
##                2.x    #7356      +/-   ##
============================================
- Coverage     54.94%   54.94%   -0.01%     
  Complexity     7415     7415              
============================================
  Files          1181     1181              
  Lines         42136    42136              
  Branches       4945     4945              
============================================
- Hits          23152    23151       -1     
- Misses        16803    16808       +5     
+ Partials       2181     2177       -4     

see 4 files with indirect coverage changes

Impacted file tree graph

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jsbxyyx
Copy link
Member

jsbxyyx commented May 21, 2025

The base property is Deprecated. suggest use branch

https://docs.codecov.com/docs/codecov-yaml#default-branch

https://docs.codecov.com/docs/commit-status#branches

Copy link
Contributor

@funky-eyes funky-eyes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please register this PR in the 2.x.md

@funky-eyes funky-eyes added this to the 2.5.0 milestone May 21, 2025
@funky-eyes funky-eyes added the type: bug Category issues or prs related to bug. label May 21, 2025
@YongGoose
Copy link
Member Author

YongGoose commented May 21, 2025

Please register this PR in the 2.x.md

I just got home! 🥹
I’ll review that comment first and then make the addition.

@YongGoose
Copy link
Member Author

@funky-eyes @jsbxyyx

PTAL ⚡️

@YongGoose
Copy link
Member Author

I think we can merge this PR once we confirm that Codecov is working properly.

@YongGoose YongGoose requested review from funky-eyes and jsbxyyx May 21, 2025 10:15
codecov.yml Outdated
if_not_found: success
target: 2.x
changes: yes #only care the changed files
changes: true
Copy link
Member Author

@YongGoose YongGoose May 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like this setting was added to limit the comparison to only the modified files, but in reality, it behaves differently.

It actually detects changes in code coverage even for lines that weren’t directly modified in the PR or commit.

So I think we need to decide whether to keep it or remove it. What are your thoughts?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this prompt keeps appearing, I decided to delete the codecov/changes stage. I think we should revert it back to "no". I don't believe we need this stage as it doesn't seem to provide any positive value.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in bf14d74 !

Copy link
Contributor

@funky-eyes funky-eyes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@funky-eyes funky-eyes merged commit d6a29b4 into apache:2.x May 21, 2025
9 checks passed
slievrly pushed a commit to slievrly/fescar that referenced this pull request Oct 21, 2025
YvCeung pushed a commit to YvCeung/incubator-seata that referenced this pull request Dec 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: bug Category issues or prs related to bug.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants