Skip to content

Introduce unit test for ConcurrentModificationException [JENKINS-76294]#183

Open
jimklimov wants to merge 2 commits intojenkinsci:masterfrom
jimklimov:JENKINS-76294-CME-test
Open

Introduce unit test for ConcurrentModificationException [JENKINS-76294]#183
jimklimov wants to merge 2 commits intojenkinsci:masterfrom
jimklimov:JENKINS-76294-CME-test

Conversation

@jimklimov
Copy link

Catching up for PR #181 and issue #180, here is a unit test that should reproduce the issue https://issues.jenkins.io/browse/JENKINS-76294 with current code base.

This commit will be included into PR #181 to check whether(/that) it solves the problem. This here PR is needed to check that the test does fail (confirm the problem) on Jenkins CI farm too. The fix will be in the other PR (to be confirmed by passing this test).

Note that relevant pom.xml bits were copied from Lockable Resource and Cucumber Reports plugins (along with the convoluted test to force the race condition and crash the best we can).

Signed-off-by: Jim Klimov <jimklimov+jenkinsci@gmail.com>
…seems we can not always collect from systemErrTap [JENKINS-76294]

Signed-off-by: Jim Klimov <jimklimov+jenkinsci@gmail.com>
@jimklimov
Copy link
Author

Did not crash :(
But might have not collected JVM console logs (stderr tap) from Jenkins, sometimes the error is only seen there. Could be because of junit4 tests and jupiter (junit5) variant of stubs. Will check on that theory later...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant