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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/23306?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 
[#23306](https://codecov.io/gh/apache/shardingsphere/pull/23306?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (9335626) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/bbcaa32c0e3798d8be6bf2372c4069613494d536?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (bbcaa32) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #23306   +/-   ##
   =========================================
     Coverage     49.86%   49.86%           
     Complexity     2455     2455           
   =========================================
     Files          4029     4029           
     Lines         57876    57876           
     Branches       9190     9190           
   =========================================
     Hits          28861    28861           
     Misses        26463    26463           
     Partials       2552     2552           
   ```
   
   
   
   :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