ovirt-engine build failure

Sandro Bonazzola sbonazzo at redhat.com
Tue Feb 18 14:37:29 UTC 2014 

Il 18/02/2014 13:32, Vojtech Szocs ha scritto:
> 
> 
> ----- Original Message -----
>> From: "Eyal Edri" <eedri at redhat.com>
>> To: "Alon Bar-Lev" <alonbl at redhat.com>
>> Cc: "Juan Hernandez" <jhernand at redhat.com>, "arch" <arch at ovirt.org>, "Kiril Nesenko" <knesenko at redhat.com>
>> Sent: Tuesday, February 18, 2014 10:46:58 AM
>> Subject: Re: ovirt-engine build failure
>>
>>
>>
>> ----- Original Message -----
>>> From: "Alon Bar-Lev" <alonbl at redhat.com>
>>> To: "Sandro Bonazzola" <sbonazzo at redhat.com>
>>> Cc: "Juan Hernandez" <jhernand at redhat.com>, "Kiril Nesenko"
>>> <knesenko at redhat.com>, "Eyal Edri" <eedri at redhat.com>,
>>> "David Caro" <dcaroest at redhat.com>, "arch" <arch at ovirt.org>
>>> Sent: Tuesday, February 18, 2014 11:37:41 AM
>>> Subject: Re: ovirt-engine build failure
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
>>>> To: "Alon Bar-Lev" <alonbl at redhat.com>
>>>> Cc: "Juan Hernandez" <jhernand at redhat.com>, "Kiril Nesenko"
>>>> <knesenko at redhat.com>, "Eyal Edri" <eedri at redhat.com>,
>>>> "David Caro" <dcaroest at redhat.com>, "arch" <arch at ovirt.org>
>>>> Sent: Tuesday, February 18, 2014 11:36:29 AM
>>>> Subject: Re: ovirt-engine build failure
>>>>
>>>> Il 18/02/2014 09:49, Alon Bar-Lev ha scritto:
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
>>>>>> To: "Juan Hernandez" <jhernand at redhat.com>, "Alon Bar-Lev"
>>>>>> <alonbl at redhat.com>
>>>>>> Cc: "Kiril Nesenko" <knesenko at redhat.com>, "Eyal Edri"
>>>>>> <eedri at redhat.com>,
>>>>>> "David Caro" <dcaroest at redhat.com>, "arch"
>>>>>> <arch at ovirt.org>
>>>>>> Sent: Tuesday, February 18, 2014 10:13:54 AM
>>>>>> Subject: ovirt-engine build failure
>>>>>>
>>>>>> Hi, we hit again an issue that comes up really often while building
>>>>>> ovirt-engine in jenkins,
>>>>>> especially when we're in a hurry because we're releasing.
>>>>>>
>>>>>> http://jenkins.ovirt.org/job/manual-build-tarball/212/label=fedora19-host/console
>>>>>>
>>>>>> IIRC it may be a corrupted artifact or an error in maven dependency
>>>>>> resolution.
>>>>>> Can we find a way for having it fixed once for ever?
>>>>>
>>>>> We are using a local artifactory mirror, so having corruption is
>>>>> unlikely.
>>>>> I think that maven checks sha1 of artifacts and reports corruption
>>>>> issue
>>>>> before trying to use.
>>>>> In this case something is failing at gwt generation, I am unsure if it
>>>>> is
>>>>> not related to resources.
>>>>
>>>> The weird thing is that it may fail on the same point for a tenth of
>>>> times
>>>> and then build successfully on the exact same host.
>>>> And that's the only job running on a 4 core i7 processor with 16 GB of
>>>> ram.
>>>
>>> With or without cleaning up the workspace?
>>
>> it also failed on a baremetal host locally. http://pastebin.com/07wANdVG
> 
> To me it seems like error during GWT compilation, i.e. invocation of gwt-maven-plugin's compile goal that performs GWT compilation.
> 
> Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.5.1:compile (gwtcompile) on project webadmin: Command [[
> ...
> ]] failed with status 1
> 
> Can we re-run this build with mvn -X flag to see debug-level Maven logs?

I'm not sure how to set it.
On my minidell:

export MAVEN_OPTS="${MAVEN_OPTS} -X -XX:MaxPermSize=1024m -Dgwt.compiler.localWorkers=3 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp"
rpmbuild -ta ovirt-engine-3.4.0_beta3.tar.gz
causes:

# we must exclude tmp.repos directory so we
# won't get artifacts of older branches
# we should use search MAVEN_OUTPUT_DIR as it may contain
# pre-compiled artifacts at different hierarchy.
install -dm 0755 "/root/rpmbuild/BUILDROOT/ovirt-engine-3.4.0-0.11.beta3.fc19.x86_64/usr/share/ovirt-engine/modules"
find "." -name '*-modules.zip' | grep -v tmp.repos | xargs -n 1 unzip -q -o -d
"/root/rpmbuild/BUILDROOT/ovirt-engine-3.4.0-0.11.beta3.fc19.x86_64/usr/share/ovirt-engine/modules"
UnZip 6.00 of 20 April 2009, by Info-ZIP.  Maintained by C. Spieler.  Send
bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

Usage: unzip [-Z] [-opts[modifiers]] file[.zip] [list] [-x xlist] [-d exdir]
  Default action is to extract files in list, except those in xlist, to exdir;
  file[.zip] may be a wildcard.  -Z => ZipInfo mode ("unzip -Z" for usage).

  -p  extract files to pipe, no messages     -l  list files (short format)
  -f  freshen existing files, create none    -t  test compressed archive data
  -u  update files, create if necessary      -z  display archive comment only
  -v  list verbosely/show version info       -T  timestamp archive to latest
  -x  exclude files that follow (in xlist)   -d  extract files into exdir
modifiers:
  -n  never overwrite existing files         -q  quiet mode (-qq => quieter)
  -o  overwrite files WITHOUT prompting      -a  auto-convert any text files
  -j  junk paths (do not make directories)   -aa treat ALL files as text
  -U  use escapes for all non-ASCII Unicode  -UU ignore any Unicode fields
  -C  match filenames case-insensitively     -L  make (some) names lowercase
  -X  restore UID/GID info                   -V  retain VMS version numbers
  -K  keep setuid/setgid/tacky permissions   -M  pipe through "more" pager
See "unzip -hh" or unzip.txt for more help.  Examples:
  unzip data1 -x joe   => extract all files except joe from zipfile data1.zip
  unzip -p foo | more  => send contents of foo.zip via pipe into program more
  unzip -fo foo ReadMe => quietly replace existing ReadMe if archive file newer
make: *** [install_artifacts] Error 123






> 
> Looking at [1] I have some questions/comments:
> 
> * I don't see any "-Dgwt.userAgent=..." override, shouldn't Makefile ensure this is set properly?
>   Without this, oVirt GUI is compiled for *all* browsers supported by GWT SDK, which increases compilation time & memory usage.
>   Note that oVirt GUI should be compiled *only* for following browsers [2]: ie8,ie9,gecko1_8,safari,opera
> 
> * maybe set "-Dgwt.compiler.localWorkers=..." to #_of_logical_CPUs available on that host
>   Higher value means faster compilation but can increase memory usage (until we move away from JVM-based worker processes)
> 
> [1] http://jenkins.ovirt.org/job/manual-build-tarball/212/label=fedora19-host/consoleFull
> [2] frontend/webadmin/modules/pom.xml -> gwt.userAgent property -> lists all supported browsers
> 
> Vojtech
> 
>>  
>>
>>>
>>>>
>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sandro Bonazzola
>>>>>> Better technology. Faster innovation. Powered by community
>>>>>> collaboration.
>>>>>> See how it works at redhat.com
>>>>>>
>>>>
>>>>
>>>> --
>>>> Sandro Bonazzola
>>>> Better technology. Faster innovation. Powered by community collaboration.
>>>> See how it works at redhat.com
>>>>
>>>
>> _______________________________________________
>> Arch mailing list
>> Arch at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/arch
>>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
> 


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

More information about the Arch mailing list