codecov-commenter commented on PR #21931:
URL: https://github.com/apache/shardingsphere/pull/21931#issuecomment-1303043373

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/21931?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 Report
   > Merging 
[#21931](https://codecov.io/gh/apache/shardingsphere/pull/21931?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (ef4d049) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/9b046d579f107d916fdfc480ce91e2230f6c984c?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (9b046d5) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #21931   +/-   ##
   =========================================
     Coverage     61.49%   61.49%           
     Complexity     2468     2468           
   =========================================
     Files          4106     4106           
     Lines         57197    57197           
     Branches       9679     9679           
   =========================================
     Hits          35176    35176           
     Misses        19158    19158           
     Partials       2863     2863           
   ```
   
   
   
   :mega: We’re building smart automated test selection to slash your CI/CD 
build times. [Learn 
more](https://about.codecov.io/iterative-testing/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to