You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:26:02 UTC

[jira] [Issue Comment Deleted] (MESOS-8923) Naked expectations can lead to flaky tests.

     [ https://issues.apache.org/jira/browse/MESOS-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated MESOS-8923:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> Naked expectations can lead to flaky tests.
> -------------------------------------------
>
>                 Key: MESOS-8923
>                 URL: https://issues.apache.org/jira/browse/MESOS-8923
>             Project: Mesos
>          Issue Type: Task
>          Components: test
>            Reporter: Alexander Rukletsov
>            Priority: Major
>              Labels: integration, mesosphere
>
> There are several cases when too general expectations can be triggered by related but not targeted events. Examples:
> 1. Resent task status update before ack due to clock manipulation
> 2. Advancing clock with {{registration_backoff_factor}} to ensure successful registration might lead to a case where the first agent resends registration request and hence satisfies the expectation for the second agent.
> A possible solution would be extensive use of matchers and extra primitives wrapping them. For example, a possible approach to 1. is https://reviews.apache.org/r/63577/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)