You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2018/09/25 07:47:00 UTC
[jira] [Updated] (OOZIE-3352) [tests]
TestCallableQueueService#testPriorityExecutionOrder() is flaky
[ https://issues.apache.org/jira/browse/OOZIE-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andras Piros updated OOZIE-3352:
--------------------------------
Summary: [tests] TestCallableQueueService#testPriorityExecutionOrder() is flaky (was: TestCallableQueueService#testPriorityExecutionOrder() is failing with ConcurrentModification)
> [tests] TestCallableQueueService#testPriorityExecutionOrder() is flaky
> ----------------------------------------------------------------------
>
> Key: OOZIE-3352
> URL: https://issues.apache.org/jira/browse/OOZIE-3352
> Project: Oozie
> Issue Type: Sub-task
> Components: tests
> Affects Versions: trunk
> Reporter: Julia Kinga Marton
> Assignee: Peter Bacsko
> Priority: Major
> Attachments: OOZIE-3352-001.patch, OOZIE-3352-002.patch
>
>
> During last few precommit runs, {{org.apache.oozie.service.TestCallableQueueService#testPriorityExecutionOrder()}} failed with {{ConcurrentModificationException}}:
> {noformat}
> [ERROR] testPriorityExecutionOrder(org.apache.oozie.service.TestCallableQueueService) Time elapsed: 20.999 s <<< ERROR!
> java.util.ConcurrentModificationException
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
> ...
> at java.util.Collections.min(Collections.java:599)
> at org.apache.oozie.service.TestCallableQueueService.testPriorityExecutionOrder(TestCallableQueueService.java:993)
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)