It already existed, because an earlier regression job ran that script on the same node:
http://traf-testlogs.esgyn.com/Daily-master/101/regress-privs2-cdh-rh6/build_regr_test_env.log --Steve > -----Original Message----- > From: Hans Zeller [mailto:[email protected]] > Sent: Thursday, June 8, 2017 8:38 AM > To: [email protected] > Subject: RE: Trafodion master rh6 Daily Test Result - 101 - Failure > > Hi, as far as I can tell, this failure is caused by a pre-existing TPC-DS > Hive table > on the Jenkins server: > > + /home/jenkins/workspace/core-regress-hive- > cdh/traf_run/sql/scripts/install_hadoop_regr_test_env -- > unpackDir=/home/jenkins/workspace/core-regress-hive-cdh/tpcds-tool -- > dataDir=/home/jenkins/workspace/core-regress-hive-cdh/tpcds-data '-- > hdfsCmd=sudo -n -u trafodion /usr/bin/hdfs' '--hiveCmd=sudo -n -u > trafodion /usr/bin/hive' --logFile=/home/jenkins/workspace/core-regress- > hive-cdh/build_regr_test_env.log > > Hive table ship_mode found. Skipping TPC-DS set-up. > > Let's hope the test passes next time we run this. > > Thanks, > > Hans > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Thursday, June 8, 2017 5:17 AM > To: [email protected] > Subject: Trafodion master rh6 Daily Test Result - 101 - Failure > > Daily Automated Testing master rh6 > > Jenkins Job: https://jenkins.esgyn.com/job/Check-Daily-master-rh6/101/ > Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/101 > Bld Downloads: http://traf-builds.esgyn.com > > Changes since previous daily build: > [Hans Zeller] [TRAFODION-2636] Memory leak in metadata context > > > > Test Job Results: > > FAILURE core-regress-hive-cdh (50 min) > SUCCESS build-rh6-master-debug (38 min) > SUCCESS build-rh6-master-release (37 min) > SUCCESS core-regress-charsets-cdh (40 min) > SUCCESS core-regress-charsets-hdp (59 min) > SUCCESS core-regress-compGeneral-cdh (1 hr 4 min) > SUCCESS core-regress-compGeneral-hdp (1 hr 5 min) > SUCCESS core-regress-core-cdh (1 hr 13 min) > SUCCESS core-regress-core-hdp (1 hr 15 min) > SUCCESS core-regress-executor-cdh (1 hr 35 min) > SUCCESS core-regress-executor-hdp (1 hr 58 min) > SUCCESS core-regress-fullstack2-cdh (9 min 50 sec) > SUCCESS core-regress-fullstack2-hdp (20 min) > SUCCESS core-regress-hive-hdp (1 hr 13 min) > SUCCESS core-regress-privs1-cdh (1 hr 10 min) > SUCCESS core-regress-privs1-hdp (1 hr 24 min) > SUCCESS core-regress-privs2-cdh (1 hr 10 min) > SUCCESS core-regress-privs2-hdp (1 hr 31 min) > SUCCESS core-regress-qat-cdh (32 min) > SUCCESS core-regress-qat-hdp (23 min) > SUCCESS core-regress-seabase-cdh (1 hr 37 min) > SUCCESS core-regress-seabase-hdp (2 hr 12 min) > SUCCESS core-regress-udr-cdh (28 min) > SUCCESS core-regress-udr-hdp (42 min) > SUCCESS jdbc_test-cdh (34 min) > SUCCESS jdbc_test-hdp (42 min) > SUCCESS phoenix_part1_T2-cdh (1 hr 10 min) > SUCCESS phoenix_part1_T2-hdp (1 hr 25 min) > SUCCESS phoenix_part1_T4-cdh (1 hr 13 min) > SUCCESS phoenix_part1_T4-hdp (1 hr 30 min) > SUCCESS phoenix_part2_T2-cdh (1 hr 3 min) > SUCCESS phoenix_part2_T2-hdp (1 hr 31 min) > SUCCESS phoenix_part2_T4-cdh (1 hr 6 min) > SUCCESS phoenix_part2_T4-hdp (1 hr 21 min) > SUCCESS pyodbc_test-cdh (16 min) > SUCCESS pyodbc_test-hdp (25 min)
