-
-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[JENKINS-57993] Avoid printing stack traces for some common agent conditions #4066
Conversation
Downstream still occasionally fails with this race condition (as the agent is being deleted):
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine with me, but would benefit from a review by @jeffret-b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm in favor. I've noticed there are quite a few messages that are more severe than justified. They show up under normal or harmless situations but confuse people and clutter logs. I've cleaned up some in various PRs. These ones look like good improvements also.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐝 quick look, nothing seems wrong.
[JENKINS-57993] Avoid printing stack traces for some common agent conditions (cherry picked from commit dcc395b)
See JENKINS-57993. In the spirit of jenkinsci/remoting#274 etc.
Proposed changelog entries