Tanzu Framework provides a set of building blocks to build atop of the Tanzu platform and leverages Carvel packaging and plugins to provide users with a much stronger, more integrated experience than the loose coupling and stand-alone commands of the previous generation of tools.
By looking at the codecov report for Tanzu Framework, the latest commits that picked up was from about month ago.
The reason TF is no longer producing unit test reports for CodeCov is this history: In two different PRs, the list of files that CodeCov read to get unit test data were first moved (PR #4541), and then deleted (PR #4583) as part of refactoring and cleanup work.
The file that was deleted that had the CodeCov list used to be at .github/workflows/unittests.yaml. It got moved in the first PR to .github/old_workflows/unittests.yaml, then it got deleted in the second.
Affected product area (please put an X in all that apply)
( ) APIs
( ) Addons
( ) CLI
( ) Docs
( ) IAM
( ) Installation
( ) Plugin
( ) Security
(x) Test and Release
( ) User Experience
( ) Developer Experience
Expected behavior
I expect latest commits to TF to have unit test reports.
Steps to reproduce the bug
Version (include the SHA if the version is not obvious)
Environment where the bug was observed (cloud, OS, etc)
Bug description
By looking at the codecov report for Tanzu Framework, the latest commits that picked up was from about month ago.
The reason TF is no longer producing unit test reports for CodeCov is this history: In two different PRs, the list of files that CodeCov read to get unit test data were first moved (PR #4541), and then deleted (PR #4583) as part of refactoring and cleanup work.
The file that was deleted that had the CodeCov list used to be at
.github/workflows/unittests.yaml
. It got moved in the first PR to.github/old_workflows/unittests.yaml
, then it got deleted in the second.Affected product area (please put an X in all that apply)
Expected behavior I expect latest commits to TF to have unit test reports.
Steps to reproduce the bug
Version (include the SHA if the version is not obvious)
Environment where the bug was observed (cloud, OS, etc)
Relevant Debug Output (Logs, manifests, etc)