Possible.  It also could have been masked by out of memory in java objects
heap space. But, what is not clear why is the expected file change needed in
master and not in release 2.0.

Selva

-----Original Message-----
From: Sandhya Sundaresan [mailto:[email protected]]
Sent: Friday, May 27, 2016 7:51 AM
To: [email protected]
Subject: RE: Trafodion master Daily Test Result - 219 - Still Failing

 RE: Trafodion master Daily Test Result - 219 - Still Failing

The failure today seems like it may be an expected file change.  Tere have
been a couple of changes related to hive access in the last week or so.

1666,1667d1665

< *** WARNING[6008] Statistics for column (CA_ADDRESS_SK) from table
HIVE.HIVE.UNLOAD_CUSTOMER_ADDRESS were not available. As a result, the
access path chosen might not be the best possible.

<

*http://traf-testlogs.esgyn.com/Daily-master/219/regress-hive-cdh/sql-regress-logs/hive/DIFF018*
<http://traf-testlogs.esgyn.com/Daily-master/219/regress-hive-cdh/sql-regress-logs/hive/DIFF018>

I wonder if it was masked by the other port issue so far.

Sandhya

-----Original Message-----
From: [email protected] [mailto:[email protected]
<[email protected]>]
Sent: Friday, May 27, 2016 4:41 AM
To: [email protected]
Subject: Trafodion master Daily Test Result - 219 - Still Failing

Daily Automated Testing master

Jenkins Job:   https://jenkins.esgyn.com/job/Check-Daily-master/219/

Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/219

Bld Downloads: http://traf-builds.esgyn.com

Changes since previous daily build:

[dbirdsall] [TRAFODION-2004] UPDATE STATS not supported on volatile tables

[dbirdsall] Update SQL reference manual.

[selvaganesang] [TRAFODION-2015] hive/TEST018 fails in daily build
regressions


Test Job Results:

FAILURE core-regress-hive-cdh (38 min)

SUCCESS build-master-debug (26 min)

SUCCESS build-master-release (31 min)

SUCCESS core-regress-charsets-cdh (32 min) SUCCESS core-regress-charsets-hdp
(49 min) SUCCESS core-regress-compGeneral-cdh (37
min) SUCCESS core-regress-compGeneral-hdp (54 min) SUCCESS
core-regress-core-cdh (43 min) SUCCESS core-regress-core-hdp (1 hr 3 min)
SUCCESS core-regress-executor-cdh (1 hr 3 min) SUCCESS
core-regress-executor-hdp (1 hr 26 min) SUCCESS core-regress-fullstack2-cdh
(14 min) SUCCESS core-regress-fullstack2-hdp (13 min) SUCCESS
core-regress-hive-hdp (43 min) SUCCESS core-regress-privs1-cdh (36 min)
SUCCESS core-regress-privs1-hdp (48 min) SUCCESS core-regress-privs2-cdh
(42 min) SUCCESS core-regress-privs2-hdp (52 min) SUCCESS
core-regress-qat-cdh (21 min) SUCCESS core-regress-qat-hdp (27 min) SUCCESS
core-regress-seabase-cdh (57 min) SUCCESS core-regress-seabase-hdp (1 hr 15
min) SUCCESS core-regress-udr-cdh (24 min) SUCCESS core-regress-udr-hdp (30
min) SUCCESS jdbc_test-cdh (32 min) SUCCESS jdbc_test-hdp (44 min) SUCCESS
phoenix_part1_T2-cdh (57 min) SUCCESS phoenix_part1_T2-hdp (1 hr 18 min)
SUCCESS phoenix_part1_T4-cdh (51 min) SUCCESS phoenix_part1_T4-hdp (1 hr 17
min) SUCCESS phoenix_part2_T2-cdh (55 min) SUCCESS phoenix_part2_T2-hdp (1
hr 17 min) SUCCESS phoenix_part2_T4-cdh (55 min) SUCCESS
phoenix_part2_T4-hdp (1 hr 19 min) SUCCESS pyodbc_test-cdh (10 min) SUCCESS
pyodbc_test-hdp (15 min)

Reply via email to