Re: Icedtea compilation issue

[Julien Rabier <taziden@xxxxxxxxxx>]

Do you think that the gigantic logged output could be the cause of the
OOM we are noticing in syslog ? (causing init to be killed, etc)



Le 22 oct. à 16:10, rcx a écrit :
>    IcedTea is a fairly intensive build.  Just to illustrate, the log file is
>    about 15 MB [ http://bb.slitaz.org/log/icedtea6-jdk.log ].
>     
>    While I don't see a timestamp recorded at the beginning of the log, some
>    of IcedTea's build step output a log timestamp, so based on the earliest
>    of those timestamps and the "compiled on" timestamp logged after
>    compilation completes (before packaging), just that part took an hour and
>    a half. 
>     
>    In reviewing the most recent log file, it appears that the build itself
>    was successful but the JVM_BUILDDIR path has changed.  IcedTea has changed
>    its output path to the following:
>        /home/slitaz/wok/icedtea6-jdk/icedtea6-1.9.1/openjdk.build/j2sdk-image/
>     
>    The receipt is still looking for files on IcedTea's prior output path:
>        $src/openjdk/build/linux-i586/j2sdk-image
>     
>    Obviously, the tail end of that path has changed.  I'm not able to do so
>    at the moment, but I'll try to get that receipt updated.  This shouldn't
>    need to be blocked.
>     
>     
>    Thanks!
>     
>    From: Christopher Rogers
>    Sent: Friday, October 22, 2010 3:32 PM
>    To: slitaz@xxxxxxxxxxxxxxxxxxx
>    Subject: Re: Icedtea compilation issue
>    I agree. The weird thing is today icedtea was build though again. But only
>    package a corrupted package with no files in it. But at least it didn't
>    crash the server. 
> 
>    I will block it myself and the other wanted packages of icedtea.
> 
>    On Fri, Oct 22, 2010 at 7:24 PM, Julien Rabier <taziden@xxxxxxxxxx> wrote:
> 
>      Hi,
> 
>      Once again, tank was offline for some hours. And once again, icedtea
>      seems to
>      be guilty as it was the package being compiled when tank crashed.
> 
>      Does anyone have an idea of what can be happening ?
> 
>      While we don't have a workaround, I suggest to "block" icedtea
>      compilation on
>      tank and compile it on an other machine, a trusted one. It's not perfect
>      but
>      I hope it will throw away some frustration.
> 
>      What do you all think about that ?
>      Julien
> 
>      -----BEGIN PGP SIGNATURE-----
>      Version: GnuPG v1.4.10 (GNU/Linux)
> 
>      iQEcBAEBAgAGBQJMweT8AAoJEH7pNufaG1AW+4QH+wfclrYk1frCUJBPgKBIuRVf
>      OAnkMMRdxnqLEhaSU/BWzrM6EG5e6XAov9Hu+0R0kSDjA/ste5LlmaZs3/IRsSNX
>      HOCLt+3mKz+OR0mub2zdV2kP/LnC6RKU5KHT4kHtzE0gnYqcl1humrZVNMjv7u0n
>      V3WbDD/a66bv5wzWgnFJEuaj+WNip6oUAE9NC2LwIohj3jXiO8prMsC19kB51Tb5
>      Z7EYT+XTsO/JZBbGPVQSNM08GIuOr93LXidlH8r2MenIW576zRxQxxu9QRj4vIJB
>      64bIFpFC/PH5ih/l+QIAi7B0G8yeUlkdFN8qCx2hn2LLodrkXYg+suC3XftUU/c=
>      =IQhH
>      -----END PGP SIGNATURE-----

Attachment: signature.asc
Description: Digital signature