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


On Mon, May 23, 2011 at 2:57 PM, Bjoern Michaelsen
<bjoern.michaelsen@canonical.com> wrote:

I'd like to see build-break mails with the error actually
inline in them as a first step.
This may simply be a outcome of parallel builds ? As a quick-fix maybe
having the buildbots auto restart with a single proc build would
resolve that in that case.
Sounds good. Norberts proposal is also good, even if a little bit more
work.

Colan asked, coalan shall receive:
bootstrap: 727609cc3c4270ca2b1c1ccb2f58502f4defc707

accumulate the output of each failed modules into a single file.
technically the output could get interleaved but it is actually
fairly unlikely, as it would required that the 2 failed module finish
exactly at the
same time and that the 2 cat that copy their respective output into
build_error.log race each other...
If that is, nevertheless, a problem, it is possible to had some
locking to prevent that

I need to adjust the tinderbox script to take advantage of that new file.

Norbert

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.