-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 flaky test by sorting slices #5171
Conversation
TestGetVarSubstitutionExpressionsForPipelineResult was flaky since the expected test output was in a fixed order while the function under test was iterating through a map where order is not guaranteed. This commit fixes it by sorting the inputs to cmp.Diff Signed-off-by: Dibyo Mukherjee <[email protected]>
/kind flake |
/test check-pr-has-kind-label |
@dibyom: The specified target(s) for
The following commands are available to trigger optional jobs:
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
you'll also have to change the v1 package unfortunately
FYI @Yongxuanzhang
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop, lbernick The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I don't see a resultref in the v1 package. Is that intentional? (I also don't see a CRD struct in result ref - maybe we could just move it out of v1beta1?) |
/lgtm
oops-- should have looked more carefully
good idea! |
oh thank you! |
Changes
TestGetVarSubstitutionExpressionsForPipelineResult was flaky since the expected
test output was in a fixed order while the function under test was iterating
through a map where order is not guaranteed. This commit fixes it by sorting
the inputs to cmp.Diff
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes