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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/23412?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 
[#23412](https://codecov.io/gh/apache/shardingsphere/pull/23412?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (63b61f7) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/6b6571e18e13c526ca079044d578a6da0337d1d2?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (6b6571e) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #23412   +/-   ##
   =========================================
     Coverage     49.82%   49.82%           
     Complexity     2461     2461           
   =========================================
     Files          4080     4080           
     Lines         58258    58258           
     Branches       9249     9249           
   =========================================
     Hits          29026    29026           
     Misses        26677    26677           
     Partials       2555     2555           
   ```
   
   
   
   :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