Re: how to track down parallel build issues?

Am Mon, 12 Apr 2010 14:33:17 +0200
schrieb Petr Mladek <[email protected]>:
 
> What do you mean with "I can build the package with -j1"? Do you mean
> that the error does not happen when you build with -j1?

Yes. Build finished when built non-smp.

> 
> > > Do you see the same problem with all .jar files or only with the
> > > LuceneHelpWrapper.jar?
> >
> > only with LuceneHelpWrapper.jar:
> >
> > register component
> > 'file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.0.10/build/ooo320-m12/so
> >lver/320/unxlngx6.pro/bin/LuceneHelpWrapper.jar' in registry
> > '/tmp/ooopackaging/i_181801270835143/unxlngx6.pro/OpenOffice//gid_Starregis
> >try_Services_Rdb_servicesrdb/en-US_inprogress_1/services.rdb'
> >failed! error
> > (CannotRegisterImplementationException):
> 
> Unfortunately, there is not useful error message.
> 
> > Not sure if this is caused by the issue above.
> >
> > > What JDK you are using?
> >
> > [andyrtr@workstation64 ~]$ java -version
> > java version "1.6.0_17"
> > OpenJDK Runtime Environment (IcedTea6 1.7.3)
> > (ArchLinux-6.b17_1.7.3-1-x86_64) OpenJDK 64-Bit Server VM (build
> > 14.0-b16, mixed mode)
> 
> Looks good.

This has changes meanwhile to:
[andyrtr@workstation64 trunk]$ java -version
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8) (ArchLinux-6.b18_1.8-1-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)

I don't run into the lucene issue right now but something that looks similar:

register component 'file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/XSLTFilter.jar' in registry '/tmp/ooopackaging/i_299191274275391/unxlngx6.pro/OpenOffice//gid_Starregistry_Services_Rdb_servicesrdb/en-US_inprogress_1/services.rdb' succesful!
ERROR:  /tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/regcomp -register -br /tmp/ooopackaging/i_299191274275391/unxlngx6.pro/OpenOffice//gid_Starregistry_Services_Rdb_servicesrdb/en-US_inprogress_1/regcomp.rdb -r /tmp/ooopackaging/i_299191274275391/unxlngx6.pro/OpenOffice//gid_Starregistry_Services_Rdb_servicesrdb/en-US_inprogress_1/services.rdb -c 'file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/agenda.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/fax.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/form.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver
 /320/unxlngx6.pro/bin/letter.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/LuceneHelpWrapper.jar;file:///tmp/go-openoffice/trunk/src/
 ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/query.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/report.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/ScriptFramework.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/ScriptProviderForBeanShell.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/ScriptProviderForJava.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/ScriptProviderForJavaScript.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/table.jar;fi
 le:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/web.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unx
 lngx6.pro/bin/XMergeBridge.jar;file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/XSLTFilter.jar' -l com.sun.star.loader.Java2 -wop='vnd.sun.star.expand:$OOO_BASE_DIR/program/classes/' -env:URE_INTERNAL_JAVA_DIR='file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin' 2>&1 |
Systemcall:  /tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/regcomp -register -br /tmp/ooopackaging/i_299191274275391/unxlngx6.pro/OpenOffice//gid_Starregistry_Services_Rdb_servicesrdb/en-US_inprogress_1/regcomp.rdb -r /tmp/ooopackaging/i_299191274275391/unxlngx6.pro/OpenOffice//gid_Starregistry_Services_Rdb_servicesrdb/en-US_inprogress_1/services.rdb -c 'file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/XSLTValidate.jar' -l com.sun.star.loader.Java2 -wop='vnd.sun.star.expand:$OOO_BASE_DIR/program/classes/' -env:URE_INTERNAL_JAVA_DIR='file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin' 2>&1 |
file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/XSLTValidate.jar
register component
'file:///tmp/go-openoffice/trunk/src/ooo-build-3.2.1.1/build/ooo320-m17/solver/320/unxlngx6.pro/bin/XSLTValidate.jar'
in registry
'/tmp/ooopackaging/i_299191274275391/unxlngx6.pro/OpenOffice//gid_Starregistry_Services_Rdb_servicesrdb/en-US_inprogress_1/services.rdb'
succesful!

This happened with ooo-build 3.2.1.1/m17 here. Maybe that's something different.

Should I try the patching again to get a strace.log?

And yes, I'm building official packages for ArchLinux. Several branches:
Usually vanilla stable released, latest testing (m18 now) and development version (m78) + latest stable bugfix release from go-openoffice/ooo-build.

The smp install trouble doesn't happen in the vanilla versions. Is there a way to prevent smp usage for the install process?

make -j1 DESTDIR=${pkgdir} install || return 1  - that doesn't help here.

The build is configured --with-max-jobs=${MAKEFLAGS/-j/} where I usually build -j6.

-Andy