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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/23238?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 
[#23238](https://codecov.io/gh/apache/shardingsphere/pull/23238?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (1455009) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/b8e24e026aa91db64ee3e027d9a9d4880b5b4158?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (b8e24e0) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #23238   +/-   ##
   =========================================
     Coverage     49.89%   49.89%           
     Complexity     2453     2453           
   =========================================
     Files          4021     4021           
     Lines         57537    57537           
     Branches       9132     9132           
   =========================================
     Hits          28706    28706           
     Misses        26289    26289           
     Partials       2542     2542           
   ```
   
   
   
   :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