Seems to be epel repo issue. I was thinking we'd wait for next daily build, but can run another if needed.
--Steve > -----Original Message----- > From: Selva Govindarajan <[email protected]> > Sent: Tuesday, April 9, 2019 9:19 AM > To: [email protected] > Subject: RE: Trafodion master rh6 Daily Test Result - 773 - Failure > > External > > It looks like there was some problem while downloading/installing the > needed package for Trafodion installation. I am assuming that this issue is > transient. > > Steve, > > Is it possible to restart the daily build again or will it be ok if the daily > build > kicks in tomorrow. > > Selva > > -----Original Message----- > From: [email protected] <[email protected]> > Sent: Tuesday, April 9, 2019 2:46 AM > To: [email protected] > Subject: Trafodion master rh6 Daily Test Result - 773 - Failure > > External > > Daily Automated Testing master rh6 > > Jenkins Job: https://jenkins.esgyn.com/job/Check-Daily-master-rh6/773/ > Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/773 > Bld Downloads: http://traf-builds.esgyn.com > > Changes since previous daily build: > [selvaganesang] Optimizing and avoiding unnecessary function calls shown as > hot spots in > > [selvaganesang] Optimizing and avoiding unnecessary function calls shown as > hot spots in > > [selvaganesang] Cleaned up and ensured that JDBC driver conforms to > transaction handling > > [selvaganesang] Optimizing and avoiding unnecessary function calls shown as > hot spots in > > [selvaganesang] Optimizing and avoiding unnecessary function calls shown as > hot spots in > > [selvaganesang] Fix to ensure that trafci returns the correct status message > of the > > [selvaganesang] Fix to ensure infostats command from trafci works as > expected. > > [selvaganesang] Fix for the failure of testLTrimFunction, testTrimFunction > and > > [selvaganesang] Fix for phoenix T2 tests in FunkyNamesTest > > [selvaganesang] [TRAFODION-3280] Reduce path length in Trafodion for > improved > > [dbirdsall] [TRAFODION-3294] Updated Messages Guide for some binder > messages > > > > Test Job Results: > > FAILURE core-regress-charsets-cdh (10 min) > FAILURE core-regress-charsets-hdp (10 min) > FAILURE core-regress-compGeneral-cdh (9 min 29 sec) > FAILURE core-regress-compGeneral-hdp (3 min 19 sec) > FAILURE core-regress-core-cdh (6 min 1 sec) > FAILURE core-regress-core-hdp (10 min) > FAILURE core-regress-executor-cdh (8 min 47 sec) > FAILURE core-regress-executor-hdp (30 min) > FAILURE core-regress-fullstack2-cdh (6 min 8 sec) > FAILURE core-regress-fullstack2-hdp (9 min 25 sec) > FAILURE core-regress-hive-cdh (9 min 41 sec) > FAILURE core-regress-hive-hdp (9 min 27 sec) > FAILURE core-regress-privs1-cdh (5 min 14 sec) > FAILURE core-regress-privs1-hdp (3 min 54 sec) > FAILURE core-regress-privs2-cdh (8 min 26 sec) > FAILURE core-regress-privs2-hdp (8 min 53 sec) > FAILURE core-regress-qat-cdh (5 min 32 sec) > FAILURE core-regress-qat-hdp (11 min) > FAILURE core-regress-seabase-cdh (9 min 17 sec) > FAILURE core-regress-seabase-hdp (3 min 23 sec) > FAILURE core-regress-udr-cdh (5 min 15 sec) > FAILURE core-regress-udr-hdp (3 min 49 sec) > FAILURE jdbc_test-cdh (6 min 12 sec) > FAILURE jdbc_test-hdp (3 min 26 sec) > FAILURE phoenix_part1_T2-cdh (5 min 44 sec) > FAILURE phoenix_part1_T2-hdp (3 min 32 sec) > FAILURE phoenix_part1_T4-cdh (8 min 52 sec) > FAILURE phoenix_part1_T4-hdp (3 min 50 sec) > FAILURE phoenix_part2_T2-cdh (5 min 49 sec) > FAILURE phoenix_part2_T2-hdp (3 min 35 sec) > FAILURE phoenix_part2_T4-cdh (9 min 47 sec) > FAILURE phoenix_part2_T4-hdp (9 min 26 sec) > FAILURE pyodbc_test-cdh (5 min 37 sec) > FAILURE pyodbc_test-hdp (3 min 28 sec) > SUCCESS build-rh6-master-debug (33 min) > SUCCESS build-rh6-master-release (38 min)
