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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/20779?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 
[#20779](https://codecov.io/gh/apache/shardingsphere/pull/20779?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (47313fb) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/59329e91a1e514a48ae94a79f6766283ff3c5ede?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (59329e9) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #20779   +/-   ##
   =========================================
     Coverage     61.31%   61.31%           
     Complexity     2419     2419           
   =========================================
     Files          3987     3987           
     Lines         55237    55237           
     Branches       9372     9372           
   =========================================
     Hits          33866    33866           
     Misses        18489    18489           
     Partials       2882     2882           
   ```
   
   
   
   :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