-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Ubuntu 9.04 (jaunty)
kernel linux 2.6.28-18 server
GNOME 2.26.1
The Hudson Warnings pluging crash when checking warnings after build step.
See attached crash dump file.
Hudson version is 1.379.
Warnings Plug-in version is 3.11,
In general Hudson and it's plugings are up to date.
Issue is present since several weeks.
Tried downgrade to plugin 3.9 and 3.10 without success.
Also tried to switch to sun-java6-jdk 6.20 instead of openjdk-6-jdk 6b18.
Nor increasing JAVA_ARGS to "-Xmx2560m" doesnt solve the problem.
- duplicates
-
JENKINS-7178 Regular expression of Doxygen parser is too complex for JDK pattern
-
- Resolved
-
[JENKINS-7687] CLONE -Hudson Warning Plugin crash, java.lang.StackOverflowError
Attachment | New: log.txt [ 19837 ] |
Description |
Original:
The Hudson Warnings pluging crash when checking warnings during build. See attached crash dump file. Hudson version is 1.370. Warnings Plug-in version is 3.8, In general Hudson and it's plugings are up to date. In general we are running all jobs in slave computers. I think, when the Warnings pluging 3.8 was installed this crash occurred. When this same Warnings pluging is running on Windows environment, it doesn't crash. |
New:
The Hudson Warnings pluging crash when checking warnings after build step. See attached crash dump file. Hudson version is 1.379. Warnings Plug-in version is 3.11, In general Hudson and it's plugings are up to date. Issue is present since several weeks. Tried downgrade to plugin 3.9 and 3.10 without success. Also tried to switch to sun-java6-jdk 6.20 instead of openjdk-6-jdk 6b18. Nor increasing JAVA_ARGS to "-Xmx2560m" doesnt solve the problem. |
Environment | Original: Redhat Enterprise Linux 5.1 |
New:
Ubuntu 9.04 (jaunty) kernel linux 2.6.28-18 server GNOME 2.26.1 |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Workflow | Original: JNJira [ 137788 ] | New: JNJira + In-Review [ 204597 ] |
What is the reason for creating this issue? Is there something different to the cloned issue?