hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <>
Subject [jira] [Updated] (HIVE-13916) Reduce the max runtime of a test further
Date Thu, 02 Jun 2016 02:05:59 GMT


Siddharth Seth updated HIVE-13916:
    Attachment: HIVE-13916.01.patch

Simple patch - pretty much a replica of HIVE-13520, but with a different value.
This adds one more fix to to get the log line to print correctly.

Not submitting to jenkins since it will have no affect, and none of ptest2 tests are run on

Tests pass locally, except the usual spark test (for which some profile probably needs to
be activated)
Results :

Failed tests:   testBatch(org.apache.hive.ptest.execution.TestScripts): expected:<... -o
-name spark.log [| \(..)
  testAlternativeTestJVM(org.apache.hive.ptest.execution.TestScripts): expected:<... -o
-name spark.log [| \(..)

Tests run: 68, Failures: 2, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:01.890s
[INFO] Finished at: Wed Jun 01 19:04:40 PDT 2016
[INFO] Final Memory: 25M/310M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test
(default-test) on project hive-ptest: There are test failures.
[ERROR] Please refer to /Users/sseth/work2/projects/hive/dev/forMvnInstall/testutils/ptest2/target/surefire-reports
for the individual test results.
[ERROR] -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following
[ERROR] [Help 1]
[INFO] Build failures were ignored.

> Reduce the max runtime of a test further
> ----------------------------------------
>                 Key: HIVE-13916
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-13916.01.patch
> HIVE-13520 reduced this from 2h to 1h.
> We should bring it down further - 40minutes.
> From logs added in HIVE-13507 - the following are the longest runtimes from run 476.
> {code}
>  ElapsedTime(seconds)=979
>  ElapsedTime(seconds)=1011
>  ElapsedTime(seconds)=1014
>  ElapsedTime(seconds)=1060
>  ElapsedTime(seconds)=1114
>  ElapsedTime(seconds)=1157
>  ElapsedTime(seconds)=1169
>  ElapsedTime(seconds)=1240
>  ElapsedTime(seconds)=1307
>  ElapsedTime(seconds)=1325
>  ElapsedTime(seconds)=1326
>  ElapsedTime(seconds)=1334
>  ElapsedTime(seconds)=1368
>  ElapsedTime(seconds)=1372
>  ElapsedTime(seconds)=1395
>  ElapsedTime(seconds)=1434
>  ElapsedTime(seconds)=1459
>  ElapsedTime(seconds)=1492
>  ElapsedTime(seconds)=1499
>  ElapsedTime(seconds)=1604
>  ElapsedTime(seconds)=3601
>  ElapsedTime(seconds)=3601
>  ElapsedTime(seconds)=3601
> {code}
> The last 3 are tests that timed out. 
> The longest valid test takes 1604 seconds or about 26 minutes. 1.5 times that is 40,
which seems like a reasonable number.
> With the current state of the builds - if the last 3 tests were not timing out - the
build/test-run would complete 20minutes faster. 
> There's two more stragglers before that - which add another 15 minutes to the test run.
i.e. if we can fix some of these longer running tests, or have them trigger early - we can
likely reduce the jenkins runtime further - TestParseNegative (1368s runtime) and TestHBaseMinimrCliDriver
(1060seconds runtime)

This message was sent by Atlassian JIRA

View raw message