Introduce unit tests at all, make one for ConcurrentModificationException [JENKINS-76294]#537
Open
jimklimov wants to merge 1 commit intojenkinsci:masterfrom
Open
Introduce unit tests at all, make one for ConcurrentModificationException [JENKINS-76294]#537jimklimov wants to merge 1 commit intojenkinsci:masterfrom
jimklimov wants to merge 1 commit intojenkinsci:masterfrom
Conversation
Author
|
Et voila, the test failed (in the expected manner exposing the original bug) with existing code base on Jenkins CI too: https://ci.jenkins.io/job/Plugins/job/cucumber-reports-plugin/job/PR-537/1/testReport/net.masterthought.jenkins/ConcurrentModificationExceptionTest/ |
6 tasks
…tion [JENKINS-76294] Signed-off-by: Jim Klimov <jimklimov+jenkinsci@gmail.com>
9bee298 to
df360ed
Compare
Member
|
Did you review failing builds? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Catching up for PR #536 and issue #336, here is a unit test that does reproduce the issue https://issues.jenkins.io/browse/JENKINS-76294 with current code base (at least it did fail on first try in my laptop).
This commit will be included into PR #536 to check whether(/that) it solves the problem.
Note that previously this repository had no tests, so relevant
pom.xmlbits were copied from Lockable Resource plugin (along with the convoluted test to force the race condition and crash the best we can). Thepom.xmlchanges in particular may be a bit of overkill for this one test case, pulling in components that are not really referenced (I did not investigate deeper). They might be useful if someone adds other tests later though.