hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-14681) Remove AssertionError for non zero return codes in QTestUtil cleanup
Date Thu, 01 Sep 2016 15:53:22 GMT


Hive QA commented on HIVE-14681:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 10435 tests executed
*Failed tests:*
TestBeeLineWithArgs - did not produce a TEST-*.xml file
TestHiveCli - did not produce a TEST-*.xml file

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 5 tests failed

This message is automatically generated.

ATTACHMENT ID: 12826495 - PreCommit-HIVE-MASTER-Build

> Remove AssertionError for non zero return codes in QTestUtil cleanup
> --------------------------------------------------------------------
>                 Key: HIVE-14681
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Testing Infrastructure
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-14681.01.patch
> This was added in HIVE-14625.
> Causes some tests to fail randomly - after executing all the actual queries.
> Shows up as 
> {code}
> {code}
> without any test name.
> The failures are related to the inability to drop databases. I suspect this has something
to do with specific q files running grant etc statements.
> Will create a separate jira to track this down.
> Fow now, I think it makes sense to convert the Assertion to a warning.
> {code}java.lang.AssertionError: Failed during cleanup processLine with code=403{code}
> {code}2016-08-31T11:47:05,627 ERROR [adab525e-198b-49f9-a2c3-8cc7df47b8ea main] ql.Driver:
Authorization failed:No privilege 'Drop' found for outputs { database:default, table:src}.
Use SHOW GRANT to get more details.{code}
> {code}java.lang.AssertionError: Failed during cleanup processLine with code=40000{code}
> {code}2016-08-31T11:41:29,849 ERROR [3906df31-d034-4dfe-8f78-239140c686aa main] ql.Driver:
FAILED: HiveAccessControlException Permission denied: Principal [name=user1, type=USER] does
not have following privileges for operation DROPTABLE [[OBJECT OWNERSHIP] on Object [type=TABLE_OR_VIEW,
> Permission
denied: Principal [name=user1, type=USER] does not have following privileges for operation
DROPTABLE [[OBJECT OWNERSHIP] on Object [type=TABLE_OR_VIEW, name=default.src]]
> 	at
> 	at
> 	at
> 	at
> 	at org.apache.hadoop.hive.ql.Driver.doAuthorizationV2(
> 	at org.apache.hadoop.hive.ql.Driver.doAuthorization(
> 	at org.apache.hadoop.hive.ql.Driver.compile(
> 	at org.apache.hadoop.hive.ql.Driver.compile(
> 	at org.apache.hadoop.hive.ql.Driver.compileInternal(
> 	at org.apache.hadoop.hive.ql.Driver.runInternal(
> 	at
> 	at
> 	at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(
> 	at org.apache.hadoop.hive.cli.CliDriver.processCmd(
> 	at org.apache.hadoop.hive.cli.CliDriver.processLine(
> 	at org.apache.hadoop.hive.cli.CliDriver.processLine(
> 	at org.apache.hadoop.hive.ql.QTestUtil.cleanUp(
> 	at org.apache.hadoop.hive.ql.QTestUtil.cleanUp(
> 	at org.apache.hadoop.hive.ql.QTestUtil.shutdown(
> 	at org.apache.hadoop.hive.cli.control.CoreCliDriver$6.invokeInternal(
> 	at org.apache.hadoop.hive.cli.control.CoreCliDriver$6.invokeInternal(
> 	at org.apache.hadoop.hive.util.ElapsedTimeLoggingWrapper.invoke(
> 	at org.apache.hadoop.hive.cli.control.CoreCliDriver.shutdown(
> 	at org.apache.hadoop.hive.cli.control.CliAdapter$1$1.evaluate(
> 	at org.junit.rules.RunRules.evaluate(
> 	at
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(
> 	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(
> 2016-08-31T11:41:29,849  INFO [3906df31-d034-4dfe-8f78-239140c686aa main] metadata.Hive:
Dumping metastore api call timing information for : compilation phase
> {code}

This message was sent by Atlassian JIRA

View raw message