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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/23090?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 
[#23090](https://codecov.io/gh/apache/shardingsphere/pull/23090?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (f1c1952) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/7a26934769728c4e6e4b467470a8a0fe77920cb6?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (7a26934) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #23090   +/-   ##
   =========================================
     Coverage     49.96%   49.96%           
     Complexity     2426     2426           
   =========================================
     Files          4110     4110           
     Lines         57395    57395           
     Branches       9063     9063           
   =========================================
     Hits          28679    28679           
     Misses        26206    26206           
     Partials       2510     2510           
   ```
   
   
   
   :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