-
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
[receiver/hostmetrics] Unit tests don't match implementation for darwin #19141
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@8naama, do you have a chance to submit a PR to update the tests? |
I can pick this up if @8naama does not respond. |
Thanks, @astencel-sumo. Assigned to you |
hey guys @dmitryax @astencel-sumo, really sorry! I completely missed this! |
No worries @8naama, great to see you back! 😄 If you can contribute the fix, that would be great 👍 |
@astencel-sumo yes you can assign to me 🙏🏼 |
Thanks, @8naama. Assigned to you |
Solved in #20538 |
Thank you so much @8naama. Looking forward to your future contributions! 🙂 |
Thank you @astencel-sumo!! :) |
Component(s)
receiver/hostmetrics
What happened?
Description
Since #18723, a subset of process metrics is supported on Darwin. When I run unit tests locally on a Mac, the
processscraper/TestCreateResourceMetricsScraper
test fails because the method no longer returns an error. Additionally, theskipTestOnUnsupportedOS
helper disables tests for metrics that are now supported on Darwin.Steps to Reproduce
On Darwin, run unit tests from the
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver
package.Expected Result
Tests pass, and all metrics supported on Darwin are tested.
Actual Result
The
TestCreateResourceMetricsScraper
test fails, mostprocess_scraper
methods are not tested.Collector version
11f8ed1
Environment information
Environment
OS: macOS 13.2.1
Compiler(if manually compiled): go 1.20.1
OpenTelemetry Collector configuration
No response
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: