• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Component/s: junit-plugin, test-stability-plugin
• Labels:

  None
• Environment:

  Ubuntu 14.04; Jenkins version 2.32.2; Java 1.8

[JENKINS-41901] Junit plugin appears hung during Pipeline step

Erik Lattimore created issue - 2017-02-09 17:13

Erik Lattimore made changes - 2017-02-09 17:13

Assignee

Original: Sean Flanigan [ seanf ]

Erik Lattimore made changes - 2017-02-09 17:14

Environment

Original: Ubuntu server Jenkins version 1.635

New: Ubuntu 14.04; Jenkins version 2.32.2; Java 1.8

Erik Lattimore made changes - 2017-02-09 17:15

Description

Original: We heavily use the Junit plugin in our jobs to record our test results as part of our CD/CI pipeline Recently we hit over 10154 tests now, which is contained in about 50 junit.xml files we copy to the jenkins workspace of the job to have them recorded We use the jenkins junit post build step to record with these params Test report XMLs = **/*.xml Health report amplification factor =1.0 Additional test report features = Allow claiming of failed tests & Test stability History We have had some regressions in our pipeline causing lots of tests to fail, today we had 235 failures, and the jenkins junit plugin blocked our job for 7 hours to complete the recording of the test results... this was crazy long, and "Aborting/canceling" the jenkins job did nothing, so we just had to wait it out..... this completely blocks our pipeline I didn't see any other bugs like this in the queue, so sorry if this is a duplicate. I am wondering if one of the "AddOns" we have like Test stability History could cause this? The Job console log literally took 7 hours to complete Recording test results Found 5922 test results Found failed test junit/com.ibm.test.......... Anything we can do to fix this or make it so this doesn't happen we are willing to try, or ideas around this, as it pretty much blocks our entire pipeline, and if you want more info or debug etc, just let me know what you want and I can look to collect it

New: We have roughly 8,000 tests and have been using the junit step with no issue

Erik Lattimore made changes - 2017-02-09 17:15

Priority

Original: Blocker [ 1 ]

New: Major [ 3 ]

Erik Lattimore made changes - 2017-02-09 17:17

Description

Original: We have roughly 8,000 tests and have been using the junit step with no issue

New: We have roughly 8,000 tests and have been using the junit step with no issue. However, when using the snippet generator, I was able to add in the Test Stability feature but now either the junit step is taking many orders of magnitude longer (1 hr+ where usually it only takes a couple of seconds) or we are completely deadlocked. Also of note, the junit step gets called in parallel as we run our tests in parallel node blocks.

Erik Lattimore made changes - 2017-02-09 17:21

Link

New: This issue duplicates JENKINS-36956 [ JENKINS-36956 ]

Erik Lattimore made changes - 2017-02-09 17:21

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Sean Flanigan made changes - 2017-02-12 04:46

Link

New: This issue relates to JENKINS-33168 [ JENKINS-33168 ]