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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/21859?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 
[#21859](https://codecov.io/gh/apache/shardingsphere/pull/21859?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (57b8289) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/710d1419bc679f4d76a63a7f0b8c58e9bd69f8f7?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (710d141) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #21859   +/-   ##
   =========================================
     Coverage     60.98%   60.98%           
     Complexity     2451     2451           
   =========================================
     Files          4106     4106           
     Lines         57225    57225           
     Branches       9663     9663           
   =========================================
     Hits          34896    34896           
     Misses        19422    19422           
     Partials       2907     2907           
   ```
   
   
   
   :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