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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/20872?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 
[#20872](https://codecov.io/gh/apache/shardingsphere/pull/20872?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (f89ef1d) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/de7ca96033465c1c607bc3d3de6d45a7c59b418f?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (de7ca96) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #20872   +/-   ##
   =========================================
     Coverage     61.52%   61.52%           
     Complexity     2449     2449           
   =========================================
     Files          4012     4012           
     Lines         55494    55494           
     Branches       9420     9420           
   =========================================
     Hits          34141    34141           
     Misses        18469    18469           
     Partials       2884     2884           
   ```
   
   
   
   :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