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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/22525?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 
[#22525](https://codecov.io/gh/apache/shardingsphere/pull/22525?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (7368349) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/ee7db7d4390824d81a1aac4035d2bddd42954eff?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (ee7db7d) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #22525   +/-   ##
   =========================================
     Coverage     50.98%   50.98%           
     Complexity     2514     2514           
   =========================================
     Files          4185     4185           
     Lines         58237    58237           
     Branches       9902     9902           
   =========================================
     Hits          29694    29694           
     Misses        26013    26013           
     Partials       2530     2530           
   ```
   
   
   
   :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