jenkins CI fails on findbugs error 137
Description
Activity
Eyal Edri September 24, 2017 at 10:10 AM
looks like its still failing on findbugs, any thoughts or we need to upgrade the slave memory?
Eitan Raviv September 24, 2017 at 9:49 AM
yes it was rebased
Eyal Edri September 24, 2017 at 9:48 AM
was the patch rebased on latest master? to make sure the fixed are included?
In any case, I re-triggered it after rebasing, lets see how it goes.
Eitan Raviv September 24, 2017 at 9:42 AM
reopening this issue per eyal's comment because the build fails again with same error in same place
Eyal Edri September 24, 2017 at 7:10 AM
There were fixes done last week by engine maintainers to fix this issue, please re-trigger the job by either rebasing from Gerrit or using the manual trigger option from Jenkins [1].
If the job still fails, then we might need to increase the VM memory, see [2] for more info.
Please reopen this ticket if the issue still persist and we'll check the memory upgrade option.
[1] http://jenkins.ovirt.org/gerrit_manual_trigger/
[2] https://ovirt-jira.atlassian.net/browse/OVIRT-1644
Barak Korren September 24, 2017 at 7:08 AM
Could you please:
1. re-trigger the build
Please do this yourself, open a Jenkins account and a ticket to grant you the `dev` role if you can't.
Details
Assignee
infrainfraReporter
Eitan RavivEitan RavivPriority
Medium
Details
Details
Assignee
infraReporter
Eitan RavivPriority
Medium
Hi,
The build
http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/30465/
failed with the following error:
05:03:18 [ERROR] Failed to execute goal
org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (default-cli)
on project webadmin: Execution default-cli of goal
org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs failed: Java
returned: 137 -> [Help 1]
After some googling it looks like this might be an out of memory error of
the process. I understand from Alona that this is a know issue.
Could you please:
1. re-trigger the build
2. look into the issue...
Thanks,
Eitan
–
IRC: erav