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

   # 
[Codecov](https://codecov.io/gh/apache/shardingsphere/pull/22670?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 
[#22670](https://codecov.io/gh/apache/shardingsphere/pull/22670?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (53c076c) into 
[master](https://codecov.io/gh/apache/shardingsphere/commit/694bfcfc697ac71f054395ea3c0c02b600b6b104?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (694bfcf) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   ```diff
   @@            Coverage Diff            @@
   ##             master   #22670   +/-   ##
   =========================================
     Coverage     49.37%   49.37%           
     Complexity     2440     2440           
   =========================================
     Files          4108     4108           
     Lines         57437    57437           
     Branches       9841     9841           
   =========================================
     Hits          28358    28358           
     Misses        26633    26633           
     Partials       2446     2446           
   ```
   
   
   
   :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