ovirt-engine build failure

[Sandro Bonazzola]

Il 19/02/2014 12:45, Vojtech Szocs ha scritto:
> Hi, I checked GWT sources:
> 
>> [INFO] java.lang.NullPointerException: No ImageRect ever computed for removeBrickCommitRequired
>> [INFO] 	at com.google.gwt.resources.rg.ImageResourceGenerator.createAssignment(ImageResourceGenerator.java:475)
> 
> This happened because internal image cache for bundled (composite PNG) images was corrput.
> It seems to be caused by disk I/O error while reading file images/glusterAsyncTasks/remove_brick_commit_required.png
> 
>> [INFO] java.lang.NullPointerException
>> [INFO] 	at com.google.gwt.resources.rebind.context.InlineResourceContext.deploy(InlineResourceContext.java:40)
> 
> This happened because image data was null, again possible disk I/O error while reading image file.
> 
> Can we enable "TRACE" logging during GWT compilation?
> 
>   -Dgwt.logLevel=TRACE


Building master right now with your suggestions here:
http://jenkins.ovirt.org/job/manual-build-tarball/227/

# CI_MAVEN_SETTINGS=$WORKSPACE/artifactory-ovirt-org-settings.xml
# export MAVEN_OPTS="${MAVEN_OPTS} -Xmx2048M -XX:MaxPermSize=1024m -Dgwt.compiler.localWorkers=1"
# rpmbuild -D "_topdir $(pwd)/rpmbuild" -ts "${TARBALL}"
# rpmbuild -D "_topdir $(pwd)/rpmbuild" -D "ovirt_build_extra_flags -gs ${CI_MAVEN_SETTINGS} -Dgwt.userAgent=ie8,ie9,gecko1_8,safari,opera
-Dgwt.logLevel=TRACE -X" --rebuild rpmbuild/SRPMS/*.src.rpm

Let me know if you need anything else.


> 
> Vojtech
> 
> 
> ----- Original Message -----
>> From: "Vojtech Szocs" <vszocs at redhat.com>
>> To: "Sandro Bonazzola" <sbonazzo at redhat.com>
>> Cc: "Eyal Edri" <eedri at redhat.com>, "Juan Hernandez" <jhernand at redhat.com>, "Kiril Nesenko" <knesenko at redhat.com>,
>> "arch" <arch at ovirt.org>
>> Sent: Tuesday, February 18, 2014 6:54:20 PM
>> Subject: Re: ovirt-engine build failure
>>
>> In your log I see following error:
>>
>> ...
>> [INFO]    Computing all possible rebind results for
>> 'org.ovirt.engine.ui.webadmin.ApplicationResources'
>> [INFO]       Rebinding org.ovirt.engine.ui.webadmin.ApplicationResources
>> [INFO]          Invoking generator
>> com.google.gwt.resources.rebind.context.InlineClientBundleGenerator
>> [INFO]             [ERROR] Generator
>> 'com.google.gwt.resources.rebind.context.InlineClientBundleGenerator' threw
>> an exception while rebinding
>> 'org.ovirt.engine.ui.webadmin.ApplicationResources'
>> [INFO] java.lang.NullPointerException: No ImageRect ever computed for
>> removeBrickCommitRequired
>> [INFO] 	at
>> com.google.gwt.resources.rg.ImageResourceGenerator.createAssignment(ImageResourceGenerator.java:475)
>> ...
>>
>> I checked again logs at
>> http://jenkins.ovirt.org/job/manual-build-tarball/212/label=fedora19-host/consoleFull
>> and indeed there is a similar error:
>>
>> ...
>> [INFO]    Computing all possible rebind results for
>> 'org.ovirt.engine.ui.webadmin.ApplicationResources'
>> [INFO]       Rebinding org.ovirt.engine.ui.webadmin.ApplicationResources
>> [INFO]          Invoking generator
>> com.google.gwt.resources.rebind.context.InlineClientBundleGenerator
>> [INFO]             [ERROR] Generator
>> 'com.google.gwt.resources.rebind.context.InlineClientBundleGenerator' threw
>> an exception while rebinding
>> 'org.ovirt.engine.ui.webadmin.ApplicationResources'
>> [INFO] java.lang.NullPointerException
>> [INFO] 	at
>> com.google.gwt.resources.rebind.context.InlineResourceContext.deploy(InlineResourceContext.java:40)
>> ...
>>
>> NullPointerException when processing ApplicationResources but occuring from
>> different places (ImageResourceGenerator vs. InlineResourceContext)
>>
>> Now I understand why Maven build fails without any details:
>> - GWT deferred binding fails for ApplicationResources (i.e. uncaught NPE)
>> - GWT compilation proceeds, fails to link with ApplicationResources
>> - GWT compilation task fails with non-OK status code
>>
>> So the issue here is GWT deferred binding generator
>> (InlineClientBundleGenerator) failure during GWT compilation.
>>
>> GWT compiler writes extra Java files during deferred binding
>> phase, so this could point to issue with local environment..
>>
>> I will try to investigate this and look at GWT source code.


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com