You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafodion.apache.org by Sandhya Sundaresan <sa...@esgyn.com> on 2016/02/01 19:47:18 UTC

RE:executor/TEST131 failure ( Trafodion master Daily Test Result - 102)

 RE:executor/TEST131 failure ( Trafodion master Daily Test Result - 102)

Hi Roberta,

  The other executor/TEST131 failure seems to have first happened with the
attached build from 1/28. The most relevant fix there was form Eric, I
guess :* [eric.owhadi] Implement TRAFODION-1420 Use ClientSmallScanner for
small scans to*

Perhaps he should validate that the test is written properly and a special
schema is created just for the test. If there is an issue with default
schemas that is causing this, we may need a JIRA as well. Looks like you
may have found a simple testcase to show the default schema issue ?

Thanks

Sandhya

-----Original Message-----
From: Roberta Marton [mailto:roberta.marton@esgyn.com
<ro...@esgyn.com>]
Sent: Monday, February 1, 2016 8:03 AM
To: dev@trafodion.incubator.apache.org; no-reply@trafodion.org
Subject: RE: Trafodion master Daily Test Result - 102

I looked at the hive and executor failures.

The hive failure is showing 2 tables are no longer in compiler cache after

dropping the external table.   This seem to be the correct behavior.

The executor test is successfully creating a table in the main session,
however, when a new sqlci is started, it can't find it.  This may have
something to do with default schemas.  I will try to create this issue in
my environment.

    Roberta

-----Original Message-----

From: steve.varnau@esgyn.com [mailto:steve.varnau@esgyn.com
<st...@esgyn.com>]

Sent: Monday, February 1, 2016 2:50 AM

To: dev@trafodion.incubator.apache.org

Subject: Trafodion master Daily Test Result - 102

Daily Automated Testing master

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

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

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

Changes since previous daily build:

No changes

Test Job Results:

FAILURE core-regress-executor-cdh (1 hr 27 min) FAILURE
core-regress-executor-hdp (54 min) FAILURE core-regress-hive-cdh (40 min)
FAILURE core-regress-hive-hdp (39 min) SUCCESS build-master-debug (29 min)
SUCCESS build-master-release (35 min) SUCCESS core-regress-charsets-cdh (21

min) SUCCESS core-regress-charsets-hdp (26 min) SUCCESS
core-regress-compGeneral-cdh (33 min) SUCCESS core-regress-compGeneral-hdp

(35 min) SUCCESS core-regress-core-cdh (33 min) SUCCESS
core-regress-core-hdp (38 min) SUCCESS core-regress-fullstack2-cdh (14 min)
SUCCESS core-regress-fullstack2-hdp (48 min) SUCCESS core-regress-privs1-cdh

(22 min) SUCCESS core-regress-privs1-hdp (27 min) SUCCESS
core-regress-privs2-cdh (1 hr 3 min) SUCCESS core-regress-privs2-hdp (33

min) SUCCESS core-regress-qat-cdh (13 min) SUCCESS core-regress-qat-hdp (51

min) SUCCESS core-regress-seabase-cdh (1 hr 15 min) SUCCESS
core-regress-seabase-hdp (1 hr 20 min) SUCCESS core-regress-udr-cdh (13
min) SUCCESS core-regress-udr-hdp (51 min) SUCCESS jdbc_test-cdh (27 min)
SUCCESS jdbc_test-hdp (1 hr 0 min) SUCCESS phoenix_part1_T2-cdh (50 min)
SUCCESS phoenix_part1_T2-hdp (55 min) SUCCESS phoenix_part1_T4-cdh (27 min)
SUCCESS phoenix_part1_T4-hdp (1 hr 2 min) SUCCESS phoenix_part2_T2-cdh (45
min) SUCCESS phoenix_part2_T2-hdp (50 min) SUCCESS phoenix_part2_T4-cdh (1
hr 4

min) SUCCESS phoenix_part2_T4-hdp (1 hr 39 min) SUCCESS pyodbc_test-cdh (38

min) SUCCESS pyodbc_test-hdp (43 min) <<...>>