You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2018/07/11 10:41:00 UTC

[jira] [Resolved] (JAMES-2462) AbstractNotificationRegistryTest is unstable

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

Tellier Benoit resolved JAMES-2462.
-----------------------------------
    Resolution: Fixed

https://github.com/linagora/james-project/pull/1536 solved the issue

> AbstractNotificationRegistryTest is unstable
> --------------------------------------------
>
>                 Key: JAMES-2462
>                 URL: https://issues.apache.org/jira/browse/JAMES-2462
>             Project: James Server
>          Issue Type: Bug
>          Components: cassandra, JMAP
>    Affects Versions: master
>            Reporter: Tellier Benoit
>            Assignee: Antoine Duprat
>            Priority: Major
>
> AbstractNotificationRegistryTest::registerShouldWorkWithExpiracyDate have a slow percentage of chances to fail...
> A delay of one second is used. This leads to push a 1 second TTL in Cassandra.
> A quick experimentation seems to suggest TTL then expires when the next second is reach (Polling for checking expiration delay suggests we got values between 0 & 1s)... Which of course is hasardous, and lead to random test failures.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org