sfxitems.sdi

Stephan Bergmann <sbergman -AT- redhat.com>
Mon, 12 Dec 2011 21:46:30 +0100

On 12/11/2011 06:06 PM, lionel@mamane.lu wrote:

On Sun, Dec 11, 2011 at 05:48:54PM +0100, Christian Lohmaier wrote:

On Sun, Dec 11, 2011 at 10:58 AM, lionel@mamane.lu<lionel@mamane.lu>  wrote:

BTW, it took about 20 minutes for the full log to arrive at
http://tinderbox.libreoffice.org/MASTER/status.html; any reason for
such a significant delay?

The cronjob that regenerates the page
is only run every 15 minutes or so. I don't consider it a
"significant delay" when a build takes 2½-3 hours...


 From the POV of a committer that gets the "you broke the build" mail
and would like to investigate it, it can feel long (it did for me).

I can only second that. The delay adds to the confusion when trying tocorrelate information in broke-mails with information available throughthe tinderbox status page (which is often necessary in addition to theinformation in the broke-mails, to make good sense of them).


Stephan

Context

[Libreoffice] "random" build failures in sfx2/sdi/sfxitems.sdi · lionel -AT- mamane.lu
- Re: [Libreoffice] "random" build failures in sfx2/sdi/sfxitems.sdi · Christian Lohmaier
  - Re: [Libreoffice] "random" build failures in sfx2/sdi/sfxitems.sdi · lionel -AT- mamane.lu
    - Re: [Libreoffice] "random" build failures in sfx2/sdi/sfxitems.sdi · Stephan Bergmann
    - Re: [Libreoffice] "random" build failures in sfx2/sdi/sfxitems.sdi · Christian Lohmaier
      - Re: [Libreoffice] "random" build failures in sfx2/sdi/sfxitems.sdi · Thorsten Behrens
- Re: [Libreoffice] "random" build failures in sfx2/sdi/sfxitems.sdi · Jan Holesovsky

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.