Trafodion test environment

[Steve Varnau <st...@esgyn.com>]

Well folks, it looks like the new test environment is now running really
well, actually better/faster than the old environment.

The initial reliability problem bringing up Hadoop on HDP nodes was solved
with a little retry logic in the bring up script.

The first full nightly test suffered from queueing/resource issue, where
test jobs waiting for debug build gave up before the build ran.  A little
configuration tweaking resolved that.  As we see in the results below,
everything passed except a few test-cases in the hive suite on HDP node.

Besides running on the AWS platform, the other main difference is that VM
instances for both build and test jobs are created as needed to serve jobs,
and are terminated if no jobs are waiting, if they sit idle for more than
short time.

I'm currently implementing a scheme to retain the disk volumes for the
terminated instances, just in case we need to bring the instances back up to
debug failures.  It is much more cost effective to retain the storage
volumes for a time than to retain the running VMs.  Even so, they will only
be retained a relatively short time, a day or two.

--Steve


> -----Original Message-----
> From: steve.varnau@esgyn.com [mailto:steve.varnau@esgyn.com]
> Sent: Wednesday, January 6, 2016 2:53 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Trafodion master Daily Test Result - 76
>
> Daily Automated Testing master
>
> Jenkins Job:   https://jenkins.esgyn.com/job/Check-Daily-master/76/
> Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/76
> Bld Downloads: http://traf-builds.esgyn.com
>
> Changes since previous daily build:
> No changes
>
>
> Test Job Results:
>
> FAILURE core-regress-hive-hdp (1 hr 11 min)
> SUCCESS build-master-debug (30 min)
> SUCCESS build-master-release (35 min)
> SUCCESS core-regress-catman1-cdh (34 min)
> SUCCESS core-regress-catman1-hdp (1 hr 14 min)
> SUCCESS core-regress-charsets-cdh (21 min)
> SUCCESS core-regress-charsets-hdp (1 hr 3 min)
> SUCCESS core-regress-compGeneral-cdh (1 hr 11 min)
> SUCCESS core-regress-compGeneral-hdp (36 min)
> SUCCESS core-regress-core-cdh (1 hr 14 min)
> SUCCESS core-regress-core-hdp (37 min)
> SUCCESS core-regress-executor-cdh (1 hr 29 min)
> SUCCESS core-regress-executor-hdp (54 min)
> SUCCESS core-regress-fullstack2-cdh (45 min)
> SUCCESS core-regress-fullstack2-hdp (49 min)
> SUCCESS core-regress-hive-cdh (34 min)
> SUCCESS core-regress-qat-cdh (14 min)
> SUCCESS core-regress-qat-hdp (21 min)
> SUCCESS core-regress-seabase-cdh (40 min)
> SUCCESS core-regress-seabase-hdp (43 min)
> SUCCESS core-regress-udr-cdh (14 min)
> SUCCESS core-regress-udr-hdp (52 min)
> SUCCESS jdbc_test-cdh (29 min)
> SUCCESS jdbc_test-hdp (26 min)
> SUCCESS phoenix_part1_T2-cdh (51 min)
> SUCCESS phoenix_part1_T2-hdp (1 hr 22 min)
> SUCCESS phoenix_part1_T4-cdh (29 min)
> SUCCESS phoenix_part1_T4-hdp (1 hr 1 min)
> SUCCESS phoenix_part2_T2-cdh (1 hr 18 min)
> SUCCESS phoenix_part2_T2-hdp (50 min)
> SUCCESS phoenix_part2_T4-cdh (31 min)
> SUCCESS phoenix_part2_T4-hdp (1 hr 6 min)
> SUCCESS pyodbc_test-cdh (40 min)
> SUCCESS pyodbc_test-hdp (14 min)