Looking in the console log, it shows the job timing out... https://jenkins.esgyn.com/job/core-regress-executor-ahw2.2/72/console
2015-08-28 09:42:16 TEST001 2015-08-28 09:42:16 ### PASS ### 2015-08-28 11:50:08 Build timed out (after 200 minutes). Marking the build as failed. So it hung for two hours after TEST001 passed. --Steve -----Original Message----- From: Qifan Chen [mailto:[email protected]] Sent: Friday, August 28, 2015 7:13 AM To: dev <[email protected]>; [email protected] Subject: Re: Trafodion Daily Test Result - 2015-08-28_08-30-00 Hi Steve, I wonder if some of the test suites even ran to completion. For example, for the executor-ahw suite, the run sb log file has one line as follows. 08/28/15 09:40:35 (RELEASE build) 08/28/15 09:42:16 TEST001 ### PASS ### On Fri, Aug 28, 2015 at 8:59 AM, <[email protected]> wrote: > Daily Automated Testing > > Jenkins Job: https://jenkins.esgyn.com/job/Check-Daily/72/ > Archived Logs: http://traf-logs.esgyn.com/Daily/2015-08-28_08-30-00 > > Changes since previous daily build: > [qfc] fix #JIRA 1449: missing end key. > > [selvaganesang] [TRAFODION-1453] Improvements in Hive Scan > > [selvaganesang] [TRAFODION-1453] Changes to avoid scan for a range > delimiter in the buffer > > > > Test Job Results: > > FAILURE core-regress-compGeneral-ahw2.2 (1 hr 46 min) FAILURE > core-regress-compGeneral-cm5.3 (1 hr 26 min) FAILURE > core-regress-executor-ahw2.2 (3 hr 21 min) FAILURE jdbc_test-ahw2.2 (2 > hr 1 min) SUCCESS build-debug (20 min) SUCCESS build-release (21 min) > SUCCESS core-regress-catman1-ahw2.2 (2 hr 6 min) SUCCESS > core-regress-catman1-cm5.3 (1 hr 31 min) SUCCESS > core-regress-charsets-ahw2.2 (1 hr 4 min) SUCCESS > core-regress-charsets-cm5.3 (39 min) SUCCESS core-regress-core-ahw2.2 > (2 hr 26 min) SUCCESS core-regress-core-cm5.3 (1 hr 1 min) SUCCESS > core-regress-executor-cm5.3 (1 hr 30 min) SUCCESS > core-regress-fullstack2-ahw2.2 (1 hr 41 min) SUCCESS > core-regress-fullstack2-cm5.3 (21 min) SUCCESS > core-regress-hive-ahw2.2 (2 hr 34 min) SUCCESS core-regress-hive-cm5.3 > (1 hr 33 min) SUCCESS core-regress-qat-ahw2.2 (1 hr 49 min) SUCCESS > core-regress-qat-cm5.3 (35 min) SUCCESS core-regress-seabase-ahw2.2 (2 > hr 27 min) SUCCESS core-regress-seabase-cm5.3 (1 hr 15 min) SUCCESS > core-regress-udr-ahw2.2 (1 hr 6 min) SUCCESS core-regress-udr-cm5.3 > (50 min) SUCCESS jdbc_test-cm5.3 (57 min) SUCCESS > phoenix_part1_T2-ahw2.2 (2 hr 29 min) SUCCESS phoenix_part1_T2-cm5.3 > (2 hr 9 min) SUCCESS phoenix_part1_T4-ahw2.2 (1 hr 36 min) SUCCESS > phoenix_part1_T4-cm5.3 (1 hr 43 min) SUCCESS phoenix_part2_T2-ahw2.2 > (3 hr 16 min) SUCCESS phoenix_part2_T2-cm5.3 (1 hr 52 min) SUCCESS > phoenix_part2_T4-ahw2.2 (2 hr 33 min) SUCCESS phoenix_part2_T4-cm5.3 > (1 hr 24 min) SUCCESS pyodbc_test-ahw2.2 (47 min) SUCCESS > pyodbc_test-cm5.3 (20 min) > > -- Regards, --Qifan
