hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-7869) Long running tests (1) [Spark Branch]
Date Fri, 29 Aug 2014 01:05:08 GMT


Hive QA commented on HIVE-7869:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 6266 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

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: 4 tests failed

This message is automatically generated.


> Long running tests (1) [Spark Branch]
> -------------------------------------
>                 Key: HIVE-7869
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Brock Noland
>            Assignee: Suhas Satish
>         Attachments: HIVE-7869-spark.patch
> I have noticed when running the full test suite locally that the test JVM eventually
crashes. We should do some testing (not part of the unit tests) which starts up a HS2 and
runs queries on it continuously for 24 hours or so.
> In this JIRA let's create a stand alone java program which connects to a HS2 over JDBC,
creates a bunch of tables (say 100) and then runs queries until the JDBC client is killed.
This will allow us to run long running tests.

This message was sent by Atlassian JIRA

View raw message