On Tue, Aug 18, 2015 at 7:56 AM, Michael Stahl <mstahl@redhat.com> wrote:
On 10.08.2015 03:22, Norbert Thiebaud wrote:
PS: PARALLELISM=1 should _not_ be needed... we are building literally
thousands of build a month an all 3 platforms and none of these build
is running PARALLELISM=1, thankfully as the build is long enough as it
is...
it is true that it should not be needed, but when your build breaks it
will make it much more obvious *which* command failed.
or it will hide it.
either the bug is systematic and the difficulty to identify the
culprit is a display problem.. for instance Windows build are flooded
with zillions of link warning that make indeed very hard to find
the actual failure... and in debug mode the dumping of thousand of
random info: warn: message also hide the tree in the forest.
but these are also true in -j1
if the bug is not systematic it is quite possible that it will stop
showing at -j1
In any case rebuilding the entire thing with -j1 is wasteful and
discouraging and imo that should never be the 'answer'.
Norbert
Context
- Re: Debug build breaks in unit test (continued)
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.