jenkins - Findbugs java result: 137 static analysis plugin -
We are running a findbug job on Jenkins after each comment, which has been published by the Static Analysis Plugin. It usually works perfectly as expected, but from time to time (makes about 100 each time) findbugs exits with exit code 137. When this happens, it generates a completely empty findbugs.xml file
The reason for the empty XML file static analysis plugin to think that this build is not really terrible (no bugs) and This uses a new reference form, which in turn makes it unsuccessful / unstable later.
I can not find anything useful really what this exhaust code should mean, or how to stop it. I'm exploring a way to either prevent this evacuation code 137 or to take a stable analysis plugin as a result of this failure (instead of creating a new reference)
I would also like to Know what this code really is.
Job console output with exit code 137 (Job: # 1 577, no bug report)
--- Cutting - more application bug patterns - [findbugs] edu.umd.cs.findbugs.detect.MultithreadedInstance apply nl / base / rela / entities / relagroups / relationgroup enter the $ 1 [findbugs] edu.umd.cs.findbugs.detect.BadUseOfReturnValue nl / base / Rila / institution / Rilegups / Relations group $ 1 [Khojbgs] apply edu.umd.cs.findbugs.detect.methodReturn nl / base / rela / entities / relagroups / Relationship group edu.umd apply $ 1 [findbugs]. Apply cs.findbugs Detect. Aidiaiar Result Kast NL / base / Rila / Entity / Rilegups / Relationship Group $ 1 [Khojbgs] NW / Reliance / institutions / Rilegups / Relations Group edu.umd.cs.findbugs.detect.FindBadCast2 for $ 1 [Khojbgs] Applying Java results: 137 [Findbugs] Saved save.bigs.xml to find output successfully Created total time: 9 minutes 0 seconds [FINDBUGS] SearchBugs are collecting analysis files ... [FINDBUGS] All files Finding Patterns Trunk / Khojbg. XML [FINDBUGS] 1 files are parsed / data / Hudson / workspace / CRM-Faindbgs [FINDBUGS] modules / Dita / Hudson / workspace / CRM discard file -findbgs / trunk / Faidibig.aksmm because it is empty. [FINDBUGS] Computing Warning based on Reference Build # 1956 Deltaas [Analysis-Controller] Computing Alert based on reference construction deltas # 1 9 56 Collection Collections Collection Job Console Output (Job: # 1956 reports current bugs): --- harvesting --- [findbugs] edu.umd.cs.findbugs.detect.Atomicity applied nl / base / rela / entities / project $ 1 [Findbugs] edu.umd.cs.findbugs.detect.DefaultEncodingNet / base / rela / entities / project $ 1 [findbugs] 32 usecs / byte 29 msec 898 bytes 1 nl / base / rela / entities / W Project $ 1 [to pass findbugs] application] Complete analysis [findbugs] generated warning: 770 [findbugs] calculate exit code ... [findbugs] setting 'worms found' flag (1) [findbugs] extract code : 1 [findbugs] Java result: 1 [findbugs] Findbugs.xml saved output saved successful time: 9 minutes 30 seconds [FINDBUGS] Khojbgs collecting analysis files ... [FINDBUGS] all Tronjank trunk / Khojbg. XML [FINDBUGS] Find matching files 1 file Es in / data / hudson / workspace / crm-findbugs [FINDBUGS] Successfully passed file / data / modules / hudson / workspace / CRM -findbugs / trunk / fundbug of module with 770 warnings . [FINDBUGS] Computing Warning on the basis of Reference # 1955 [Analysis-Collective] Deltaas Reference # 1955 Computing Alert based on Collection Artifacts
-
If this is unsuccessful
-
Optional: Check the plugin, auto it The book, submit
-
patch
Comments
Post a Comment