-
Notifications
You must be signed in to change notification settings - Fork 137
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
## Description This is mostly about getting rid of the `-v` for all the `go test` runs. Also gets rid of the cleaning the go test cache and adds some empty lines to ci.yaml. ## Why is this needed I got rid of `-v` as its just not necessary and I feel actually hinders debugging failed tests. When the tests pass I don't really care to see *all* the tests passing, pretty sure everyone just takes it for granted that all the tests are run :D. But when a test fails then the `-v` actually hinders debugging because now you have to go and hunt for the failed test and it's output. Without the `-v` go does the sane thing of only showing the verbose output of the failed test(s). So lets just get rid of the forced `-v`. I got rid of the `go clean -testcache` calls because I have not found it to be necessary in my day-to-day development. Pretty sure a required use of `go clean -testcache` would be considered a bug in the golang/go. This change was introduced in 8ec0d84 without any reason so I'll just assume there wasn't one. ## How Has This Been Tested? Lots of `make test` and `go test ./...` for a long time without any breakage. ## How are existing users impacted? What migration steps/scripts do we need? Faster test runs (by avoiding re-testing unchanged code) and easier to find/debug test failures. ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
- Loading branch information
Showing
2 changed files
with
32 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters