You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/11/05 15:15:27 UTC
[jira] [Updated] (SLING-5060) use virtual clock for discovery tests
[ https://issues.apache.org/jira/browse/SLING-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli updated SLING-5060:
-------------------------------
Fix Version/s: (was: Discovery Impl 1.2.2)
removed fix version for now. this is test-cleanup for later.
alternatively, instead of using fixed thread.sleeps/waits we could also switch to waitUntil approach where we wait until a certain condition is hit before we continue. this would make the test perform much fast too - but still be flexible and stable when running on slower hardware.
> use virtual clock for discovery tests
> -------------------------------------
>
> Key: SLING-5060
> URL: https://issues.apache.org/jira/browse/SLING-5060
> Project: Sling
> Issue Type: Test
> Components: Extensions
> Affects Versions: Discovery Impl 1.1.6
> Reporter: Stefan Egli
> Assignee: Stefan Egli
>
> Currently there are test failures on different CI instances due to the fact that they sometimes run rather slow vs what is expected during tests. This badly affects test stability.
> An alternative to always increase the timing further and further whenever a test failure is encountered, is to use a virtual clock instead. This would allow to make very precise tests in a very fast manner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)