-
Notifications
You must be signed in to change notification settings - Fork 194
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-25406] Downgrade ISE to log warning #40
Conversation
…the log until it can be diagnosed and fixed properly.
Shouldn't break anything, so 👍 |
Could break something, in case the Maven plugin was really relying on being able to change build status after completion. Build timed out on CI. I will set the project to use a faster machine class and will file a separate PR for an unrelated test failure. |
@jglick then lets comment return and grab logging results first? |
…Result-JENKINS-25406
(now subsumes #41) |
I am not sure what that would tell us. We already have the stack traces, and they do not point to a clear culprit. Need a way to reproduce the problem. |
Hmm, for some reason PR builds do not seem to be being triggered at all ATM. |
@jglick push slowly 😆 |
👍 looks fine to me |
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
[JENKINS-25406] Downgrade ISE to log warning
JENKINS-25406
Under circumstances yet to be identified, the Maven plugin sometimes tries to set the build result after the build is
COMPLETED
, which is illegal. Until 1.586 Jenkins core silently let it do so unless you happened to be running with-ea
. As of 1.587 this becomes anIllegalStateException
, which alerted us to the problem but might be breaking more important things (unclear what the impact is). Downgrading this to a warning in the log and just ignore the attempt to change the build result.@reviewbybees