-
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
[broken test][sumologicextension] several tests failed on Windows #36481
Labels
Comments
songy23
added
flaky test
a test is flaky
os:windows
needs triage
New item requiring triage
labels
Nov 21, 2024
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was referenced Dec 9, 2024
This comment was marked as off-topic.
This comment was marked as off-topic.
nvm, turns out #36726 fixes a different issue |
sbylica-splunk
pushed a commit
to sbylica-splunk/opentelemetry-collector-contrib
that referenced
this issue
Dec 17, 2024
…y#36772) #### Description On Windows it consistently fails to get the name of certain processes, likely zombie process, reporting: "A device attached to the system is not functioning." My long term recommendation will be for the owners to directly use the Win32 API to get process information instead of the library: while it uses the correct permissions to get the process name it is not using the flag that allows to get the device name path which should avoid this issue even for zombie processes, I'm not sure if that is desirable or not. #### Link to tracking issue Fixes open-telemetry#36481 #### Testing Repro the failure locally and checked that the test passed locally with the change. I couldn't lint it locally on Windows (tool crash, will use CI to check that) #### Documentation Added changelog
mterhar
pushed a commit
to mterhar/opentelemetry-collector-contrib
that referenced
this issue
Dec 19, 2024
…y#36772) #### Description On Windows it consistently fails to get the name of certain processes, likely zombie process, reporting: "A device attached to the system is not functioning." My long term recommendation will be for the owners to directly use the Win32 API to get process information instead of the library: while it uses the correct permissions to get the process name it is not using the flag that allows to get the device name path which should avoid this issue even for zombie processes, I'm not sure if that is desirable or not. #### Link to tracking issue Fixes open-telemetry#36481 #### Testing Repro the failure locally and checked that the test passed locally with the change. I couldn't lint it locally on Windows (tool crash, will use CI to check that) #### Documentation Added changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component(s)
extension/sumologic
Describe the issue you're reporting
E.g. https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/11937483258/job/33273579980
The text was updated successfully, but these errors were encountered: