Major Description
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.
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
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)