-
Notifications
You must be signed in to change notification settings - Fork 54
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
Potential deadlock from GraphListenerAdapterToPipelineListener #700
Comments
This comment was marked as outdated.
This comment was marked as outdated.
@jglick it's in the "Issue" |
Sorry about that. I tried to follow the issue template of the project. I can make it more visible. |
@Dohbedoh @dwnusbaum do you have recommendations on how we can fix this? I looked at the logic of the code and it sounded reasonable to me. |
@cyrille-leclerc |
Thanks @dwnusbaum . |
Jenkins and plugins versions report
Environment
Issue
Jenkins shows a deadlock between open-telemetry
GraphListenerAdapterToPipelineListener
and the Jenkins initialization thread:Could be due to the usage of a synchronous GraphListener:
What Operating System are you using (both controller, and any agents involved in the problem)?
JVM Implementation
Operating system
Reproduction steps
No consistently reproducible. But basically:
Expected Results
No deadlocks
Actual Results
deadlock
Anything else?
No response
The text was updated successfully, but these errors were encountered: