We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The vipersync.TestPersistConfig tests are extremely flaky in CI, and slightly less so on a local machine.
vipersync.TestPersistConfig
We've skipped them for now, but we need to rewrite these tests to re-enable them, as that code is currently untested.
go test -race run "TestPersistConfig" ./go/viperutil/internal/vipersync
main
N/A
No response
The text was updated successfully, but these errors were encountered:
ajm188
Successfully merging a pull request may close this issue.
Overview of the Issue
The
vipersync.TestPersistConfig
tests are extremely flaky in CI, and slightly less so on a local machine.We've skipped them for now, but we need to rewrite these tests to re-enable them, as that code is currently untested.
Reproduction Steps
go test -race run "TestPersistConfig" ./go/viperutil/internal/vipersync
Binary Version
Operating System and Environment details
Log Fragments
No response
The text was updated successfully, but these errors were encountered: