You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/12/24 20:32:49 UTC
[jira] [Resolved] (JENA-1106) Make TestAlarmClock more robust to
heavily loaded CI environments.
[ https://issues.apache.org/jira/browse/JENA-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-1106.
---------------------------------
Resolution: Fixed
Fix Version/s: Jena 3.1.0
TestAlarmClock done and seen to work at least once.
> Make TestAlarmClock more robust to heavily loaded CI environments.
> ------------------------------------------------------------------
>
> Key: JENA-1106
> URL: https://issues.apache.org/jira/browse/JENA-1106
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Jena 3.1.0
>
>
> {{TestAlarmClock}} is erratic on MS Windows when the jenkins server is under load.
> Using awaitility should mean re have longer maximum timeouts without compromising the common case of on-time alarms.
> There are other places to look at as well. {{TestDatasetGraphWithLock}} (leads to {{TestDatasetGraphInMemoryLock}} and {{TestDatasetGraphInMemoryLock}}), {{TestPipedRDFIterators}} {{TestQueryExecutionTimeout1}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)