Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 8 Dec 2015 23:39:10 +0000 (UTC)
From: "Neil Conway (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12920239.1449617895000.307045.1449617950963@Atlassian.JIRA>
In-Reply-To: <JIRA.12920239.1449617895000@Atlassian.JIRA>
References: <JIRA.12920239.1449617895000@Atlassian.JIRA>
 <JIRA.12920239.1449617895094@arcas>
Subject: [jira] [Created] (MESOS-4101) Consider running most/all tests with
 the clock paused
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Neil Conway created MESOS-4101:
----------------------------------

             Summary: Consider running most/all tests with the clock paused
                 Key: MESOS-4101
                 URL: https://issues.apache.org/jira/browse/MESOS-4101
             Project: Mesos
          Issue Type: Improvement
          Components: test
            Reporter: Neil Conway


Presently, some tests pause the clock before they do timing-sensitive operations, only calling explicitly {{Clock::advance()}} to help ensure that dependencies on the clock don't cause the test to be non-deterministic. (Using {{Clock::advance()}} is typically also faster than waiting for the equivalent amount of physical time to elapse.)

However, most tests do not pause the clock, which contributes to the ongoing flakiness witnessed in many tests. We should investigate whether it is feasible to pause the clock in all/most tests (e.g., have the clock paused by default), and only enable the clock when the test cannot be implemented with {{Clock::advance()}}, {{Clock::settle()}}, and similar functions.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)