Hi all, The report for the master branch is available here: https://app.codecov.io/gh/apache/pulsar (opening the report takes some time)
Please note that the report could be inconsistent due to the scheduled master branch build failing because of flaky tests and that happens very often. In that case, the report would not be updated at all or it would be inconsistent if one of the categories (unittests, inttest, systests) fails to get uploaded. It's possible to check the state of uploads on codecov.io by clicking on the last commit hash link and viewing the uploads on the right side panel on the commit page. There should be 4 separate uploads (2 for unittests, 1 for inttests and 1 for systests). The Pulsar CI jobs for the master branch can be viewed here and retried (unless there's another scheduled master job build in progress): https://github.com/apache/pulsar/actions/workflows/pulsar-ci.yaml?query=branch%3Amaster https://github.com/apache/pulsar/actions/workflows/pulsar-ci-flaky.yaml?query=branch%3Amaster Code coverage metrics collection and reporting via codecov.io has been fixed by this PR: https://github.com/apache/pulsar/pull/24595 At the time codecov.io code coverage metrics collection was added, it required registering the project by a GitHub project admin for the apache/pulsar repository. This was requested from ASF Infra, but the request was rejected. (details in https://github.com/apache/pulsar/issues/19952#issuecomment-1488009570) codecov.io has changed their policy since then. Open source projects no longer need to be explicitly registered by an admin, and the required token for sending metrics is now available for project maintainers. The benefit of the report (https://app.codecov.io/gh/apache/pulsar) is that it's possible to find code that is not well covered by existing tests in Pulsar CI. -Lari
