[ 
https://issues.apache.org/jira/browse/HIVE-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993384#comment-16993384
 ] 

László Bodor edited comment on HIVE-22617 at 12/11/19 10:04 AM:
----------------------------------------------------------------

reproduced the original issue locally:
{code}
java.io.FileNotFoundException: Source 
'/Users/lbodor/apache/hive/itests/hive-unit/target/junit-qfile-results/clientpositive/groupby1.q.out'
 does not exist
        at 
org.apache.commons.io.FileUtils.checkFileRequirements(FileUtils.java:1383)
        at org.apache.commons.io.FileUtils.copyFile(FileUtils.java:1060)
        at org.apache.commons.io.FileUtils.copyFile(FileUtils.java:1028)
        at 
org.apache.hadoop.hive.ql.QOutProcessor.maskPatterns(QOutProcessor.java:162)
        at 
org.apache.hadoop.hive.ql.QTestUtil.checkCliDriverResults(QTestUtil.java:932)
        at 
org.apache.hadoop.hive.ql.QTestRunnerUtils.queryListRunnerMultiThreaded(QTestRunnerUtils.java:152)
        at 
org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1(TestMTQueries.java:55)
{code}
according to hive.log (attached:  [^hive.log] ), groupby1.q test hasn't been 
event started (cannot find any reference to sql statements from it in hive.log)

after test, target folder is like this:
{code}
 lbodor@HW12459  ~/apache/hive   HIVE-22617  ll 
/Users/lbodor/apache/hive/itests/hive-unit/target/junit-qfile-results/clientpositive/
total 96
-rw-r--r--  1 lbodor  staff   5.2K Dec 11 10:33 initialize.log
-rw-r--r--  1 lbodor  staff   1.1K Dec 11 10:33 input1.q.out
-rw-r--r--  1 lbodor  staff   2.2K Dec 11 10:33 input19.q.out
-rw-r--r--  1 lbodor  staff    13K Dec 11 10:33 join2.q.out
-rw-r--r--  1 lbodor  staff    13K Dec 11 10:33 join2.q.out.orig
{code}

it's very strange because it runs in a thread, and it's been waited for by 
thread.join() ...


was (Author: abstractdog):
reproduced the original issue locally:
{code}
java.io.FileNotFoundException: Source 
'/Users/lbodor/apache/hive/itests/hive-unit/target/junit-qfile-results/clientpositive/groupby1.q.out'
 does not exist
        at 
org.apache.commons.io.FileUtils.checkFileRequirements(FileUtils.java:1383)
        at org.apache.commons.io.FileUtils.copyFile(FileUtils.java:1060)
        at org.apache.commons.io.FileUtils.copyFile(FileUtils.java:1028)
        at 
org.apache.hadoop.hive.ql.QOutProcessor.maskPatterns(QOutProcessor.java:162)
        at 
org.apache.hadoop.hive.ql.QTestUtil.checkCliDriverResults(QTestUtil.java:932)
        at 
org.apache.hadoop.hive.ql.QTestRunnerUtils.queryListRunnerMultiThreaded(QTestRunnerUtils.java:152)
        at 
org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1(TestMTQueries.java:55)
{code}
according to hive.log, groupby1.q test hasn't been event started (cannot find 
any reference to sql statements from it in hive.log)

after test, target folder is like this:
{code}
 lbodor@HW12459  ~/apache/hive   HIVE-22617  ll 
/Users/lbodor/apache/hive/itests/hive-unit/target/junit-qfile-results/clientpositive/
total 96
-rw-r--r--  1 lbodor  staff   5.2K Dec 11 10:33 initialize.log
-rw-r--r--  1 lbodor  staff   1.1K Dec 11 10:33 input1.q.out
-rw-r--r--  1 lbodor  staff   2.2K Dec 11 10:33 input19.q.out
-rw-r--r--  1 lbodor  staff    13K Dec 11 10:33 join2.q.out
-rw-r--r--  1 lbodor  staff    13K Dec 11 10:33 join2.q.out.orig
{code}

it's very strange because it runs in a thread, and it's been waited for by 
thread.join() ...

> Re-Enable PreCommit test 
> org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-22617
>                 URL: https://issues.apache.org/jira/browse/HIVE-22617
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Oliver Draese
>            Assignee: László Bodor
>            Priority: Major
>         Attachments: hive.log
>
>
> The test was disabled via HIVE-22616 because it was flaky. If the test is 
> considered valid, it needs to be fixed and re-enabled.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to