You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### 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](#11221)
#### 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 [open-telemetry#11221](open-telemetry#11221)
HongChenTW
pushed a commit
to HongChenTW/opentelemetry-collector
that referenced
this issue
Dec 19, 2024
#### 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 [open-telemetry#11221](open-telemetry#11221)
Describe the bug
unit test TestProcess TelemetryWithHostProc is failing for metric name
otelcol_process_cpu_seconds
Steps to reproduce
using linux host, run
go test
insideservice/internal/proctelemetry
folderWhat did you expect to see?
expect tests to pass
What did you see instead?
What version did you use?
upstream main repo
What config did you use?
n/a
Environment
microsoft go 1.23.1 devcontainer in vs code
Additional context
failing in pipeline here: https://github.com/open-telemetry/opentelemetry-collector/actions/runs/10945728350/job/30390637590?pr=11208#step:6:634
It appears that the test is looking for the prefix "process_cpu_seconds" here:
opentelemetry-collector/service/internal/proctelemetry/process_telemetry_linux_test.go
Line 42 in 1edd311
all the metrics that it is testing start with otelcol. Will submit a PR to fix this test.
The text was updated successfully, but these errors were encountered: