codecov-commenter commented on PR #208:
URL: 
https://github.com/apache/skywalking-banyandb/pull/208#issuecomment-1308830504

   # 
[Codecov](https://codecov.io/gh/apache/skywalking-banyandb/pull/208?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 
[#208](https://codecov.io/gh/apache/skywalking-banyandb/pull/208?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (2edad4c) into 
[main](https://codecov.io/gh/apache/skywalking-banyandb/commit/99606f5f688a897bc0d5e984b00f8c7710e35170?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=The+Apache+Software+Foundation)
 (99606f5) will **not change** coverage.
   > The diff coverage is `n/a`.
   
   > :exclamation: Current head 2edad4c differs from pull request most recent 
head 3932a58. Consider uploading reports for the commit 3932a58 to get more 
accurate results
   
   ```diff
   @@           Coverage Diff           @@
   ##             main     #208   +/-   ##
   =======================================
     Coverage   44.84%   44.84%           
   =======================================
     Files          84       84           
     Lines        8500     8500           
   =======================================
     Hits         3812     3812           
     Misses       4354     4354           
     Partials      334      334           
   ```
   
   
   
   :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