-
Notifications
You must be signed in to change notification settings - Fork 35
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
fix: lingering non deterministic tests #523
Conversation
testCases := []struct { | ||
name string | ||
expedited bool | ||
}{ | ||
"regular proposal": {}, | ||
"expedited proposal": { | ||
expedited: true, | ||
}, | ||
{name: "regular proposal", expedited: false}, | ||
{name: "expedited proposal", expedited: true}, |
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.
Order matters for this tests, so we cant range over the map
[]string{ | ||
fmt.Sprintf("--%s=text", flags.FlagOutput), | ||
}, |
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.
I think depending on the order of tests run, its possible for this test to return as json if the json test runs before it, so we just specify for this to return as text
(cherry picked from commit 5efa153)
(cherry picked from commit 5efa153) Co-authored-by: Adam Tucker <[email protected]>
Description
Closes: #XXXX
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change