Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 28 Mar 2017 16:49:41 +0000 (UTC)
From: "Benjamin Bannier (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.13038279.1485467453000.144948.1490719781610@Atlassian.JIRA>
In-Reply-To: <JIRA.13038279.1485467453000@Atlassian.JIRA>
References: <JIRA.13038279.1485467453000@Atlassian.JIRA> <JIRA.13038279.1485467453443@jira-lw-us.apache.org>
Subject: [jira] [Commented] (MESOS-7016) Make default AWAIT_* duration
 configurable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 28 Mar 2017 16:49:45 -0000


    [ https://issues.apache.org/jira/browse/MESOS-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945533#comment-15945533 ] 

Benjamin Bannier commented on MESOS-7016:
-----------------------------------------

Linking MESOS-7318 which is related in the sense that test expectations might also fail when tests are run in e.g., a virtual machine which is for some reason suspended by the host.

> Make default AWAIT_* duration configurable
> ------------------------------------------
>
>                 Key: MESOS-7016
>                 URL: https://issues.apache.org/jira/browse/MESOS-7016
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess, test
>            Reporter: Benjamin Bannier
>
> libprocess defines a number of helpers {{AWAIT_*}} to wait for a {{process::Future}} reaching terminal states. These helpers are used in tests.
> Currently the default duration to wait before triggering an assertion failure is 15s. This value was chosen as a compromise between failing fast on likely fast developer machines, but also allowing enough time for tests to pass in high-contention environments (e.g., overbooked CI machines).
> If a machine is more overloaded than expected, {{Futures}} might take longer to reach the desired state, and tests could fail. Ultimately we should consider running tests with paused clock to eliminate this source of test flakiness, see MESOS-4101, but as an intermediate measure we should make the default timeout duration configurable.
> A simple approach might be to expose a build variable allowing users to set at configure/cmake time a desired timeout duration for the setup they are building for. This would allow us to define longer timeouts in the CI build scripts, while keeping default timeouts as short as possible.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)