-
-
Notifications
You must be signed in to change notification settings - Fork 36
Address ConcurrentModificationException which occasionally happens during XStream saving of running workflows [JENKINS-76294] #181
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
base: master
Are you sure you want to change the base?
Conversation
…zed [JENKINS-76294] Signed-off-by: Jim Klimov <jimklimov+jenkinsci@gmail.com>
…erialization [JENKINS-76294] Signed-off-by: Jim Klimov <jimklimov+jenkinsci@gmail.com>
… them in constructor(s) [JENKINS-76294] Signed-off-by: Jim Klimov <jimklimov+jenkinsci@gmail.com>
|
For now, posting first the proposed solution to check it would not explode on Jenkins CI farm. As noted above, maven test crashed for me locally even on master branch anyway. |
|
Apparently, current Jenkins CI farm can not build (pass tests of) the plugin too. Oh joy... |
|
Test failures as such seem to not be related to the PR change, as there are relatively few of those in https://ci.jenkins.io/job/Plugins/job/github-autostatus-plugin/job/PR-181/1/pipeline-overview/log?nodeId=53 : The I am less certain about There are however about 400 mentions of |
|
Stack traces due to the original issue were still seen after updating other plugins with CME concerns (lockable-resources here), but leaving this one at 3.6.2: Now restarted that controller with a private build bypassing the tests ( |
|
FWIW, the exception was not seen during the past week worth of builds... |
See https://issues.jenkins.io/browse/JENKINS-76294, #180 and jenkinsci/lockable-resources-plugin#825 (for example of similar problem and fix).
Testing done
So far none. The
BuildStatusAction.javadoes not seem to use aJenkinsRuleso a new test class would be needed.In fact, plugin tests failed for me locally even on the unmodified master branch, so a new failing (later fixed) test would be a bit invisible.
Submitter checklist