The coverage stats for pull request and the main branch are different. It looks like the main branch is not using the correct coverage configuration file and probably using an out-dated configuration. For example, elasticdl/python/tests folder has been ignored as specified in the configuration. However, this folder is only ignored in pull request branch but not the main branch. The coverage stat for the pull request branch is correct but not the main branch.
Steps to Reproduce
Create a pull request
Once the build passes, take a look at the coverage for this pull request branch and you’ll notice that elasticdl/python/tests folder does not appear in the report
Then compare with the coverage report for the main branch once it’s merged, elasticdl/python/tests folder still appears.
Expected behavior: The coverage stats should be the same and elasticdl/python/tests folder should be ignored for both branches.
Actual behavior: The coverage stats are not the same and elasticdl/python/tests folder is not ignored for the main branch.
Flakiness? All the time.
Please include the browser and OS and what versions you’re running.
We are adding better logging on from where the YAML file is being called in our logs, so that if the incorrect YAML file gets called we will better to be able a.) identify it and b.) surface that information back to the users.
Appreciate you sticking with us as we continue to improve!
Also, just confirming here, as with Twitter, that your original posts were flagged unexpectedly: