provider: Add -count 1 to testacc Makefile target to prevent issues with Go test caching #10245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Release note for CHANGELOG:
Go 1.10+ will automatically cache successful test results if it detects no local changes: https://golang.org/doc/go1.10#test
When running acceptance testing to attempt to find eventual consistency issues by repeatedly running the same tests, its possible this Go test caching will inadvertently make it hard to detect inconsistent remote results. The testing output does not make it obvious for individual tests (at least in Go 1.13.0) that the results are actually cached except for the final line which mentions
(cached)
:Output from acceptance testing: