[
https://issues.apache.org/jira/browse/OOZIE-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryota Egashira updated OOZIE-1405:
----------------------------------
Attachment: OOZIE-1405-part2.patch
on top of Mona's patch, i did modification. some of test failure fixed, but
still TestSLAEventGeneration.testCoordinatorActionCommands sometimes throw
following error (seemingly at tearDown, wondering whether order of service
destroy matters)
{code}
Exception in thread "pool-10-thread-1" java.lang.AbstractMethodError
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:51)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hadoop.hive.metastore.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:48)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
{code}
> Fix flakey SLA tests
> --------------------
>
> Key: OOZIE-1405
> URL: https://issues.apache.org/jira/browse/OOZIE-1405
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: trunk
>
> Attachments: 1405-part.patch, OOZIE-1405-part2.patch
>
>
> The SLA tests keep failing randomly because they rely on Thread.sleep. Would
> be better to execute all test case scenarios and then assert everything in
> order from eventQueue to avoid flakey failures.
> Similar for time-sensitive TestEventGeneration tests e.g. -
> org.apache.oozie.event.TestEventGeneration.testCoordinatorActionEvent
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
