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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/24100?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 
[#24100](https://codecov.io/gh/apache/shardingsphere/pull/24100?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (2d6db85) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/b9d3c063a8acad209cd17a5880f2f667a1999b39?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (b9d3c06) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #24100   +/-   ##
   =========================================
     Coverage     50.12%   50.12%           
     Complexity     1572     1572           
   =========================================
     Files          3253     3253           
     Lines         53395    53395           
     Branches       9819     9819           
   =========================================
     Hits          26764    26764           
     Misses        24273    24273           
     Partials       2358     2358           
   ```
   
   
   
   :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