Skip to content
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 TestProcessTelemetryWithHostProc test #11222

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jackgopack4
Copy link
Contributor

Description

Fixes failing unit test TestProcessTelemetryWithHostProc under service/internal/proctelemetry/process_telemetry_linux_test.go due to incorrect metric name

Link to tracking issue

Fixes #11221

Testing

unit tests

Documentation

none

@jackgopack4 jackgopack4 changed the title fix TestProcessTelemetryWithHostProc test [chore] fix TestProcessTelemetryWithHostProc test Sep 19, 2024
@jackgopack4 jackgopack4 marked this pull request as ready for review September 19, 2024 20:04
@jackgopack4 jackgopack4 requested a review from a team as a code owner September 19, 2024 20:04
Copy link

codecov bot commented Sep 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.80%. Comparing base (07c3e17) to head (5aa4cba).

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #11222   +/-   ##
=======================================
  Coverage   91.79%   91.80%           
=======================================
  Files         424      424           
  Lines       20094    20094           
=======================================
+ Hits        18445    18447    +2     
+ Misses       1269     1268    -1     
+ Partials      380      379    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@codeboten
Copy link
Contributor

I'm curious why this test isn't failing here: #11208

@jackgopack4
Copy link
Contributor Author

jackgopack4 commented Sep 20, 2024

Is it possible that this test is flaky in its current state, because the cpu seconds may sometimes be more than zero for these metrics, but sometimes not?

It seems from looking at it that if you want this condition to catch those specific parameters, we should add this change.

These are the parameters this test is testing, no?

@jackgopack4
Copy link
Contributor Author

seems like this test just missed getting updated when the metrics were changed to add an "otelcol_" prefix:

5753a58

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unit Test service/internal/proctelemetry/TestProcessTelemetryWithHostProc failing
2 participants