Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Enable api and manifests regeneration before testing #1007

Closed
wants to merge 1 commit into from

Conversation

souleb
Copy link
Contributor

@souleb souleb commented Jul 26, 2024

I would like to enable fmt/vet as well as updating module and regenerating apis and manifests in an automated manner as part of running tests targets.

@souleb souleb marked this pull request as draft July 26, 2024 13:26
@coveralls
Copy link
Collaborator

coveralls commented Jul 26, 2024

Pull Request Test Coverage Report for Build 10113389910

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 11 unchanged lines in 4 files lost coverage.
  • Overall coverage increased (+0.4%) to 63.877%

Files with Coverage Reduction New Missed Lines %
pkg/state/state_hostdevice_network.go 2 78.38%
controllers/hostdevicenetwork_controller.go 2 89.77%
controllers/macvlannetwork_controller.go 2 86.25%
controllers/ipoibnetwork_controller.go 5 77.38%
Totals Coverage Status
Change from base Build 10091016261: 0.4%
Covered Lines: 3252
Relevant Lines: 5091

💛 - Coveralls

…prior to running tests

Signed-off-by: Soule BA <souleb@nvidia.com>
@souleb souleb marked this pull request as ready for review July 26, 2024 15:03
@rollandf
Copy link
Member

/retest-image_scan

@@ -271,14 +271,14 @@ setup-envtest: $(SETUP_ENVTEST) ## Install envtest binaries
clean-envtest: setup-envtest ;## Clean up assets installed by setup-envtest
$Q $(SETUP_ENVTEST) cleanup

check test tests: setup-envtest ; $(info running $(NAME:%=% )tests...) @ ## Run tests
check test tests: tidy generate fmt vet manifests setup-envtest ; $(info running $(NAME:%=% )tests...) @ ## Run tests
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need to run these on make test? Won't it make running tests locally longer?
Maybe we should have build check that tidy/fmt/vet/generate are passing without any file changes, in the same manner as we have for manifests?
Here is the check for manifests: https://github.com/Mellanox/network-operator/blob/master/.github/workflows/build.yml#L52

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

time wise this is trivial compared to envtest setup and actual tests. My idea is to make sure that locally running test gives me the best possible confidence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants