Conversation
|
@jsiirola I brought this up at the dev call last week but I noticed that codecov has some new test analytics features: https://docs.codecov.com/docs/test-analytics Since this PR is already making changes to the codecov configuration, should we go ahead and enable these test analytics while we're at it? **EDIT: We discussed this during the dev call and decided that the codecode test analytics would require significant changes beyond what's included in this PR so we will move forward with this PR as-is. |
|
I did a quick look at the test analytics feature and it looks like it would require a somewhat significant restructuring of the GHA drivers to have each job always upload both coverage and the test result. Right now we bundle the codecov results into only 5 uploads because a while back CodeCov was having trouble when we uploaded all our job results individually. Given the effort, I think I would argue for doing it in a separate PR. |
Fixes # .
Summary/Motivation:
This resolves some issues with our CodeCov configuration:
codecov.yml->.codecov.ymlto clean up the project directoryChanges proposed in this PR:
Legal Acknowledgement
By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution: