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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/21221?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 
[#21221](https://codecov.io/gh/apache/shardingsphere/pull/21221?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (a0e98bd) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/9719e27aed9aaae86d805d36e2eb4d44bf3fb42c?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (9719e27) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #21221   +/-   ##
   =========================================
     Coverage     61.52%   61.52%           
     Complexity     2551     2551           
   =========================================
     Files          4092     4092           
     Lines         56396    56396           
     Branches       7503     7503           
   =========================================
     Hits          34699    34699           
     Misses        18757    18757           
     Partials       2940     2940           
   ```
   
   
   
   :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