-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[chore] Fix TestPerfCounter_Reset test #36726
[chore] Fix TestPerfCounter_Reset test #36726
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.
Ugh :( this one again... i had to fix a bunch of these because of the change in testify
@codeboten I would love to have |
CI failures:Windows failures are #36481 OPAMP failure: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/12242789600/job/34151180181?pr=36726#step:8:823
|
Thanks @pjanotti! |
#### Description Fix the TestPerfCounter_Reset that is failing consistently. ```terminal === FAIL: . TestPerfCounter_Reset (0.00s) watcher_test.go:131: Error Trace: D:/a/opentelemetry-collector-contrib/opentelemetry-collector-contrib/pkg/winperfcounters/watcher_test.go:131 Error: Both arguments must be pointers Test: TestPerfCounter_Reset ``` Root case: after upgrading `testify` circa of 2 weeks ago, since it included: > NotSame should fail if args are not pointers stretchr/testify#1661 by @sikehish in stretchr/testify#1664 See https://github.com/stretchr/testify/releases #### Testing Local test run Co-authored-by: Antoine Toulme <[email protected]>
Description
Fix the TestPerfCounter_Reset that is failing consistently.
Root case: after upgrading
testify
circa of 2 weeks ago, since it included:See https://github.com/stretchr/testify/releases
Testing
Local test run