Fang-Yu Rao created IMPALA-8880:
-----------------------------------
Summary: EventsProcessorStressTest.testUsingRandomHiveQueries
seems to be a flaky test
Key: IMPALA-8880
URL: https://issues.apache.org/jira/browse/IMPALA-8880
Project: IMPALA
Issue Type: Bug
Reporter: Fang-Yu Rao
The recently updated test EventsProcessorStressTest.testUsingRandomHiveQueries
due to https://issues.apache.org/jira/browse/IMPALA-8661 seems to be a flaky
one. Create a JIRA to track the fixing of the test file.
The related error messages are provided in the following.
{code:java}
Error while processing statement: FAILED: Execution Error, return code 1 from
org.apache.hadoop.hive.ql.exec.mr.MapRedTask.
java.util.concurrent.ExecutionException:
org.apache.hadoop.fs.FileAlreadyExistsException: rename destination
/tmp/hadoop-jenkins/mapred/local/1566309485426 already exists.
{code}
The related stack trace is also provided.
{code:java}
java.lang.AssertionError: Error while processing statement: FAILED: Execution
Error, return code 1 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask.
java.util.concurrent.ExecutionException:
org.apache.hadoop.fs.FileAlreadyExistsException: rename destination
/tmp/hadoop-jenkins/mapred/local/1566309485426 already exists.
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.impala.catalog.events.EventsProcessorStressTest.testUsingRandomHiveQueries(EventsProcessorStressTest.java:212)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143)
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
