-
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
Fixes flaky metrics unit tests #1731
Conversation
/assign |
/retest |
@hrishin you go
|
@vdemeester ohh yeah, thank you :). (need to align tooling on on dev machine) |
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.
/lgtm
Quite often unit test failure showing "*** a different view with the same name is already registered" messages at many places. At the biggning of every metrics test, it tries to register respective metrics views(metrics data it want present), publish metrics and uniregister views. Uniregister view is important becuase for next test it dont need to hold the old metrics data. unregister() views were getting called using `defer` in table test for loop, just like for _, td := range tests { defer unregister() ....... } This were resulting unwanted execution behaviour for unregister() views function, which umtimately faling tests. Its better to unregister() views before start executing the tests. This patch fixes the behaviour by calling uniregister() views function at the end of loop. Fixes tektoncd#1659
1ff9004
to
a19543d
Compare
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
Changes
Quite often unit test failure showing "*** a different view
with the same name is already registered" messages at many places.
At the beginning of every metrics test, it tries to register respective
metrics views(metrics data it want present), publish metrics and
uniregister views. Uniregister view is important becuase for next
test it dont need to hold the old metrics data.
unregister() views were getting called using
defer
intable test for loop, just like
for _, td := range tests {
defer unregister()
.......
}
This were resulting unwanted execution behaviour
for unregister() views function, which umtimately faling tests.
Its better to unregister() views before start executing the
tests.
This patch fixes the behaviour by calling uniregister() views function
at the end of loop.
Fixes #1659
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.