mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Conway (JIRA)" <>
Subject [jira] [Created] (MESOS-4101) Consider running most/all tests with the clock paused
Date Tue, 08 Dec 2015 23:39:10 GMT
Neil Conway created MESOS-4101:

             Summary: Consider running most/all tests with the clock paused
                 Key: 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

View raw message