[
https://issues.apache.org/jira/browse/YUNIKORN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167520#comment-17167520
]
Weiwei Yang commented on YUNIKORN-311:
--------------------------------------
hi [~adam.antal]
Per ticket: https://codecov.freshdesk.com/support/tickets/3556
Could you pls try this solution:
I think you might be encountering an issue I see sometimes with Travis where it
uploads on a different (merge) commit then the real one, and as such we have
trouble matching. For example, that job you linked appears to actually be
https://github.com/apache/incubator-yunikorn-core/commit/b26799db6d3de938c7316e4f2d163773aaaebf20
Is it possible for you to use the `-c` flag to the bash uploader to specify the
commit SHA and see if that changes anything?
> Code coverage is not updating for the core builds
> --------------------------------------------------
>
> Key: YUNIKORN-311
> URL: https://issues.apache.org/jira/browse/YUNIKORN-311
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: build, core - scheduler
> Affects Versions: 0.9
> Reporter: Wilfred Spiegelenburg
> Assignee: Adam Antal
> Priority: Critical
>
> Code coverage is a important phase in CI/CD, but we are missing the report
> now.
> Not sure when and how this happens, but in the past, we were able to see the
> report published to each PR.
> https://github.com/apache/incubator-yunikorn-core/blob/d2a76c0d7000bb50e377f170538938236c1144c5/Makefile#L81
> this is supposed to generate the coverage txt, and this
> https://github.com/apache/incubator-yunikorn-core/blob/d2a76c0d7000bb50e377f170538938236c1144c5/.travis.yml#L42
> is supposed to do the reporting.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
