Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi Norbert,

Caolán McNamara píše v Po 08. 11. 2010 v 13:47 +0000:

There is some improvement on the smoketest front

It run pass many more tests.. but still do not finish:

The smoketest passes every time for me. FWIW

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f0a3aab45ce, pid=31378,
tid=139682275239680

There's clearly a problem, and we should find out what it is. So...

What's your distro and version. Versions of java and versions of gcc
and glibc ?

I have spent most of today trying to get smoketest to work (initially I
had similar problems as you, on SLED11 [with some SP1 updates], x86-64),
and here are the observations:

- you do not want to do make dev-install before make smoketest
  - something gets terribly confused wrt. the links & epm packing (that
    is necessary for the smoketest itself), and the smoketest does not
    bootstrap correctly then
  - I suppose we want to get rid of unpacking of the installation sets
    for smoketest, and instead use ooinstall directly ;-)

- in a change pulled from OOo, there is some suspicious code trying to
  workaround some lifetime issues
  - I have reverted it in a local build, does not seem to help much, but
    I am not sure I did it correctly the first time I checked, so
    rebuilding again

All in all - some improvements, but still, not perfect yet ;-)

Regards,
Kendy


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.