-
Notifications
You must be signed in to change notification settings - Fork 6
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
Remove gotestfmt #1069
Remove gotestfmt #1069
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's see what this looks like!
@t0yv0, @guineveresaenger Late to the party but we've had the same issues in azure-native and I had good initial results with tparse instead. Here's a draft PR; you can look at the test results. It's essentially just regular |
Take 2 on removing gotestfmt. Since extension workflows still use it, retain the installation stanza, but not actually use in tests. pulumi/pulumi-azure-native#3404 is promising but to be evaluated later I think? Previously: #1069 #1071
Following ci-mgmt where it [was already removed](pulumi/ci-mgmt#1069).
Engineers noticing gotestfmt reporting test output in a confusing way, such as mis-attributing logs from one test to another or not reporting logs if a panic is encountered. This change removes this utility, switching to default Go test output. It also removes the
-v
flag so that the test failure output is minimally scoped to the failing tests and is easier to find. Defaults for the win.