[JIRA] (JENKINS-43775) java.util.ConcurrentModificationException when calling junit() step in parallel pipeline branch

70 views
Skip to first unread message

d.scheidl@gmx.net (JIRA)

unread,
Jul 26, 2018, 2:35:03 AM7/26/18
to jenkinsc...@googlegroups.com
Dietmar Scheidl commented on Bug JENKINS-43775
 
Re: java.util.ConcurrentModificationException when calling junit() step in parallel pipeline branch

We ran into a similar problem, one of the parallel branches failed with:

java.util.ConcurrentModificationException
	at java.util.ArrayList.sort(ArrayList.java:1464)
	at java.util.Collections.sort(Collections.java:175)
	at hudson.tasks.junit.TestResult.freeze(TestResult.java:783)
	at hudson.tasks.junit.TestResultAction.setResult(TestResultAction.java:108)
	at hudson.tasks.junit.TestResultAction.mergeResult(TestResultAction.java:270)
	at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:178)
	at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:50)
	at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:23)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49)
	at hudson.security.ACL.impersonate(ACL.java:290)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

d.scheidl@gmx.net (JIRA)

unread,
Jul 26, 2018, 2:48:03 AM7/26/18
to jenkinsc...@googlegroups.com
Dietmar Scheidl edited a comment on Bug JENKINS-43775
We ran into a similar problem, one of the parallel branches failed with:
* Jenkins 2.121.1
* JUnit Plugin 1.24

 {noformat}

java.util.ConcurrentModificationException
at java.util.ArrayList.sort(ArrayList.java:1464)
at java.util.Collections.sort(Collections.java:175)
at hudson.tasks.junit.TestResult.freeze(TestResult.java:783)
at hudson.tasks.junit.TestResultAction.setResult(TestResultAction.java:108)
at hudson.tasks.junit.TestResultAction.mergeResult(TestResultAction.java:270)
at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:178)
at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:50)
at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:23)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49)
at hudson.security.ACL.impersonate(ACL.java:290)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}

Kuypers.Dirk@googlemail.com (JIRA)

unread,
Sep 3, 2018, 8:03:02 AM9/3/18
to jenkinsc...@googlegroups.com

junit via xunit plugin seems to be affected, too:

java.util.ConcurrentModificationException

        at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)

        at java.util.ArrayList$Itr.next(ArrayList.java:859)

        at hudson.tasks.junit.TestResult.tally(TestResult.java:705)

        at hudson.tasks.junit.TestResult.merge(TestResult.java:319)

        at hudson.tasks.junit.TestResultAction.mergeResult(TestResultAction.java:269)

        at org.jenkinsci.plugins.xunit.XUnitProcessor.recordTestResult(XUnitProcessor.java:345)

        at org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:157)

        at org.jenkinsci.plugins.xunit.XUnitBuilder.perform(XUnitBuilder.java:114)

        at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)

        at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)

        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)

        at hudson.security.ACL.impersonate(ACL.java:290)

        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

Kuypers.Dirk@googlemail.com (JIRA)

unread,
Sep 4, 2018, 4:59:02 AM9/4/18
to jenkinsc...@googlegroups.com
Dirk Kuypers updated an issue
 
Jenkins / Bug JENKINS-43775
Change By: Dirk Kuypers
Priority: Minor Major

Kuypers.Dirk@googlemail.com (JIRA)

unread,
Sep 4, 2018, 5:00:03 AM9/4/18
to jenkinsc...@googlegroups.com
 
Re: java.util.ConcurrentModificationException when calling junit() step in parallel pipeline branch

I have raised the issue to a higher priority because in our case about 30 % of the builds fail due to this exception.

daniel.geissler@salt-solutions.de (JIRA)

unread,
Oct 18, 2019, 4:55:02 PM10/18/19
to jenkinsc...@googlegroups.com

Same here today in a parallel block test execution (declarative pipeline):
Jenkins: 2.176.3
JUnit Plugin : 1.27

java.util.ConcurrentModificationException
	at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
	at java.util.ArrayList$Itr.next(ArrayList.java:859)
	at hudson.tasks.junit.TestResult.getResultByNodes(TestResult.java:656)
	at hudson.tasks.junit.TestResult.getResultByNode(TestResult.java:647)
	at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:57)
	at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:23)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
 
                                                            

                                                        
 
Strange thing is that we've never had this in structural pipelines so far, although they run in parallel too.
 		 
                                                
 
                                            
                                        
 		 
                                

                        
 		 
                
 
                
 
                     
                        
 
                            
                                
 
                                     This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
                                     
                                        
 
                                            
                                                
 
                                                     Atlassian logo  
                                                
 
                                            
                                        
 		 
                                
 
                            
                        
 		 
                
 
            
        
   
    


Reply all
Reply to author
Forward
0 new messages