codecov-commenter commented on PR #139:
URL: https://github.com/apache/yunikorn-web/pull/139#issuecomment-1782137002

   ## 
[Codecov](https://app.codecov.io/gh/apache/yunikorn-web/pull/139?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)
 Report
   > Merging 
[#139](https://app.codecov.io/gh/apache/yunikorn-web/pull/139?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)
 (efcd70a) into 
[master](https://app.codecov.io/gh/apache/yunikorn-web/commit/5fa48ad6810caad581c2cdec10ff81cbbddef347?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)
 (5fa48ad) will **not change** coverage.
   > Report is 1 commits behind head on master.
   > The diff coverage is `n/a`.
   
   > :exclamation: Current head efcd70a differs from pull request most recent 
head 73ffd5c. Consider uploading reports for the commit 73ffd5c to get more 
accurate results
   
   ```diff
   @@           Coverage Diff           @@
   ##           master     #139   +/-   ##
   =======================================
     Coverage   66.66%   66.66%           
   =======================================
     Files           1        1           
     Lines          30       30           
   =======================================
     Hits           20       20           
     Misses          7        7           
     Partials        3        3           
   ```
   
   
   
   :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=apache)
   


-- 
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