[
https://issues.apache.org/jira/browse/HIVE-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165922#comment-14165922
]
Xuefu Zhang commented on HIVE-8362:
-----------------------------------
[~jxiang], the randomness of the output for this test is probably caused by the
concurrency issue in collecting linage info in move tasks. Option
hive.exec.parallel previously didn't apply to move tasks but now it does
(HIVE-8042). As a result, multiple move tasks can collect linage info
concurrently, accessing shared variable without synchronization.
> Investigate flaky test parallel.q [Spark Branch]
> ------------------------------------------------
>
> Key: HIVE-8362
> URL: https://issues.apache.org/jira/browse/HIVE-8362
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Labels: spark
>
> Test parallel.q is flaky. It fails sometimes with error like:
> {noformat}
> Failed tests:
> TestSparkCliDriver.testCliDriver_parallel:120->runTest:146 Unexpected
> exception junit.framework.AssertionFailedError: Client Execution results
> failed with error code = 1
> See ./ql/target/tmp/log/hive.log or ./itests/qtest/target/tmp/log/hive.log,
> or check ./ql/target/surefire-reports or
> ./itests/qtest/target/surefire-reports/ for specific test cases logs.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
