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


On 20 February 2018 at 10:12, Stephan Bergmann <sbergman@redhat.com> wrote:

On 17.02.2018 07:54, Noel Grandin wrote:

at the very least we should make that wait command use a timeout, and
fail the test, rather than hanging indefinitely​


As long as its unclear what the underlying problem is, what benefit does
it have to add a timeout failure path in the test?  Without the added
timeout, a local failed test will be ready to be inspected (and moggi now
gave suggestions what exactly to inspect in another mail in this thread).
And failed tests on the tinderboxes will eventually time out either way.


My thinking is that it's better to fail sooner rather than tying up the box
for the hour or so it takes before the build timeout kicks in.

But yeah, it is now harder to catch the thing locally.

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.