You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafodion.apache.org by Wei-Shiun Tsai <we...@esgyn.com> on 2016/02/18 03:33:32 UTC
Mxosrvr cores from phoenix tests
Hi,
Has anybody looked into the cores mentioned by Steve below? At some point,
a regression has started to fail phoenix tests with mxosrvr cores in our
build. I narrowed it down to a smaller java problem to reproduce it. It is
an upsert statement that has caused it. This seems to only happen with JDBC
though. I didn't see this problem when running the same statements in
sqlci. Anyone wants to take a look?
conn.createStatement().execute("create table DescColumnSortOrderTest
(id integer not null, date1 date not null, constraint pk primary key (id
desc, date1));");
pStmt = conn.prepareStatement("upsert into DescColumnSortOrderTest
(id, date1) values (?, ?)");
Object[][] rows = new Object[][]{{1, date(1, 1, 2012)}, {3, date(1, 1,
2013)}, {2, date(1, 1, 2011)}};
for (int row = 0; row < rows.length; row++) {
for (int col = 0; col < rows[row].length; col++) {
Object value = rows[row][col];
pStmt.setObject(col + 1, value);
}
pStmt.execute();
}
Thanks,
Weishiun
-----Original Message-----
From: Steve Varnau [mailto:steve.varnau@esgyn.com]
Sent: Tuesday, February 16, 2016 3:30 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Trafodion master Daily Test Result - 117
After multiple attempts to get the permissions and environment right, I've
finally got the automation generating the back-trace on the corefiles being
generated in the phoenix-part1 tests. Here is one:
http://traf-testlogs.esgyn.com/Daily-master/117/phoenix_part1_T4-hdp-2/corefiles.log
The other test jobs should be covered in tonight's build, though likely the
same results as this one.
--Steve
> -----Original Message-----
> From: steve.varnau@esgyn.com [mailto:steve.varnau@esgyn.com]
> Sent: Tuesday, February 16, 2016 2:54 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Trafodion master Daily Test Result - 117
>
> Daily Automated Testing master
>
> Jenkins Job: https://jenkins.esgyn.com/job/Check-Daily-master/117/
> Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/117
> Bld Downloads: http://traf-builds.esgyn.com
>
> Changes since previous daily build:
> No changes
>
>
> Test Job Results:
>
> FAILURE core-regress-executor-cdh (2 hr 20 min)
> FAILURE core-regress-hive-cdh (46 min)
> FAILURE core-regress-hive-hdp (39 min)
> FAILURE phoenix_part1_T2-cdh (1 hr 19 min)
> FAILURE phoenix_part1_T2-hdp (1 hr 21 min)
> FAILURE phoenix_part1_T4-cdh (37 min)
> FAILURE phoenix_part1_T4-hdp (1 hr 10 min)
> SUCCESS build-master-debug (30 min)
> SUCCESS build-master-release (35 min)
> SUCCESS core-regress-charsets-cdh (21 min)
> SUCCESS core-regress-charsets-hdp (1 hr 3 min)
> SUCCESS core-regress-compGeneral-cdh (33 min)
> SUCCESS core-regress-compGeneral-hdp (44 min)
> SUCCESS core-regress-core-cdh (38 min)
> SUCCESS core-regress-core-hdp (1 hr 20 min)
> SUCCESS core-regress-executor-hdp (54 min)
> SUCCESS core-regress-fullstack2-cdh (48 min)
> SUCCESS core-regress-fullstack2-hdp (47 min)
> SUCCESS core-regress-privs1-cdh (21 min)
> SUCCESS core-regress-privs1-hdp (1 hr 6 min)
> SUCCESS core-regress-privs2-cdh (27 min)
> SUCCESS core-regress-privs2-hdp (32 min)
> SUCCESS core-regress-qat-cdh (13 min)
> SUCCESS core-regress-qat-hdp (18 min)
> SUCCESS core-regress-seabase-cdh (1 hr 20 min)
> SUCCESS core-regress-seabase-hdp (43 min)
> SUCCESS core-regress-udr-cdh (51 min)
> SUCCESS core-regress-udr-hdp (18 min)
> SUCCESS jdbc_test-cdh (27 min)
> SUCCESS jdbc_test-hdp (29 min)
> SUCCESS phoenix_part2_T2-cdh (1 hr 21 min)
> SUCCESS phoenix_part2_T2-hdp (53 min)
> SUCCESS phoenix_part2_T4-cdh (1 hr 9 min)
> SUCCESS phoenix_part2_T4-hdp (42 min)
> SUCCESS pyodbc_test-cdh (8 min 56 sec)
> SUCCESS pyodbc_test-hdp (43 min)
RE: Mxosrvr cores from phoenix tests
Posted by Selva Govindarajan <se...@esgyn.com>.
RE: Mxosrvr cores from phoenix tests
I looked at the core file. The core file indicates that the query is
UPSERT INTO DescColumnSortOrderTest (id,date1) VALUES(?,?)
Can we attempt to reproduce this issue using sqlci?
We need to take the test case and execute the similar commands in sqlci to
check if the problem is reproducible in sqlci.
>From the core file, the current subtask is ex_root_tcb::work method. I
traversed through subtasks in the scheduler, the subtask below is strange
because it has neither the function pointer for the work method nor tcb.
This might give us some clue to the problem.
gdb) p *this->subtasks_->next_
$59 = {
_vptr.ExSubtask = 0x7fd93dc4eda0,
scheduler_ = 0x7fd92ad00998,
scheduled_ = 0,
workProc_ = 0,
tcb_ = 0x0,
next_ = 0x7fd92ad01da0,
breakPoint_ = 0,
taskName_ = 0x7fd93d9a8626 "EX"
Selva
-----Original Message-----
From: Sandhya Sundaresan [mailto:sandhya.sundaresan@esgyn.com
<sa...@esgyn.com>]
Sent: Wednesday, February 17, 2016 6:39 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Mxosrvr cores from phoenix tests
Hi Weishiun,
Yes there is a JIRA for this. JIRA TRAFODION-1825 . Arvind filed that and
I did talk to Anoop briefly about it. There was a suspicion it was checkin
for JIRA 1807. I think we need to see the exact query/string getting to SQL
upsert statement to proceed further on this since the core does not show
any datetime function.
Arvind, if you can provide that to Anoop and me, we can go from there.
Sandhya
-----Original Message-----
From: Wei-Shiun Tsai [mailto:wei-shiun.tsai@esgyn.com
<we...@esgyn.com>]
Sent: Wednesday, February 17, 2016 6:34 PM
To: dev@trafodion.incubator.apache.org
Subject: Mxosrvr cores from phoenix tests
Hi,
Has anybody looked into the cores mentioned by Steve below? At some point,
a regression has started to fail phoenix tests with mxosrvr cores in our
build. I narrowed it down to a smaller java problem to reproduce it. It
is an upsert statement that has caused it. This seems to only happen with
JDBC though. I didn't see this problem when running the same statements in
sqlci. Anyone wants to take a look?
conn.createStatement().execute("create table DescColumnSortOrderTest
(id integer not null, date1 date not null, constraint pk primary key (id
desc, date1));");
pStmt = conn.prepareStatement("upsert into DescColumnSortOrderTest
(id, date1) values (?, ?)");
Object[][] rows = new Object[][]{{1, date(1, 1, 2012)}, {3, date(1,
1, 2013)}, {2, date(1, 1, 2011)}};
for (int row = 0; row < rows.length; row++) {
for (int col = 0; col < rows[row].length; col++) {
Object value = rows[row][col];
pStmt.setObject(col + 1, value);
}
pStmt.execute();
}
Thanks,
Weishiun
-----Original Message-----
From: Steve Varnau [mailto:steve.varnau@esgyn.com <st...@esgyn.com>]
Sent: Tuesday, February 16, 2016 3:30 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Trafodion master Daily Test Result - 117
After multiple attempts to get the permissions and environment right, I've
finally got the automation generating the back-trace on the corefiles being
generated in the phoenix-part1 tests. Here is one:
http://traf-testlogs.esgyn.com/Daily-master/117/phoenix_part1_T4-hdp-2/corefiles.log
The other test jobs should be covered in tonight's build, though likely the
same results as this one.
--Steve
> -----Original Message-----
> From: steve.varnau@esgyn.com [mailto:steve.varnau@esgyn.com
<st...@esgyn.com>]
> Sent: Tuesday, February 16, 2016 2:54 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Trafodion master Daily Test Result - 117
>
> Daily Automated Testing master
>
> Jenkins Job: https://jenkins.esgyn.com/job/Check-Daily-master/117/
> Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/117
> Bld Downloads: http://traf-builds.esgyn.com
>
> Changes since previous daily build:
> No changes
>
>
> Test Job Results:
>
> FAILURE core-regress-executor-cdh (2 hr 20 min) FAILURE
> core-regress-hive-cdh (46 min) FAILURE core-regress-hive-hdp (39 min)
> FAILURE phoenix_part1_T2-cdh (1 hr 19 min) FAILURE
> phoenix_part1_T2-hdp (1 hr 21 min) FAILURE phoenix_part1_T4-cdh (37
> min) FAILURE phoenix_part1_T4-hdp (1 hr 10 min) SUCCESS
> build-master-debug (30 min) SUCCESS build-master-release (35 min)
> SUCCESS core-regress-charsets-cdh (21 min) SUCCESS
> core-regress-charsets-hdp (1 hr 3 min) SUCCESS
> core-regress-compGeneral-cdh (33 min) SUCCESS
> core-regress-compGeneral-hdp (44 min) SUCCESS core-regress-core-cdh
> (38 min) SUCCESS core-regress-core-hdp (1 hr 20 min) SUCCESS
> core-regress-executor-hdp (54 min) SUCCESS core-regress-fullstack2-cdh
> (48 min) SUCCESS core-regress-fullstack2-hdp (47 min) SUCCESS
> core-regress-privs1-cdh (21 min) SUCCESS core-regress-privs1-hdp (1 hr
> 6 min) SUCCESS core-regress-privs2-cdh (27 min) SUCCESS
> core-regress-privs2-hdp (32 min) SUCCESS core-regress-qat-cdh (13 min)
> SUCCESS core-regress-qat-hdp (18 min) SUCCESS core-regress-seabase-cdh
> (1 hr 20 min) SUCCESS core-regress-seabase-hdp (43 min) SUCCESS
> core-regress-udr-cdh (51 min) SUCCESS core-regress-udr-hdp (18 min)
> SUCCESS jdbc_test-cdh (27 min) SUCCESS jdbc_test-hdp (29 min) SUCCESS
> phoenix_part2_T2-cdh (1 hr 21 min) SUCCESS phoenix_part2_T2-hdp (53
> min) SUCCESS phoenix_part2_T4-cdh (1 hr 9 min) SUCCESS
> phoenix_part2_T4-hdp (42 min) SUCCESS pyodbc_test-cdh (8 min 56 sec)
> SUCCESS pyodbc_test-hdp (43 min)
RE: Mxosrvr cores from phoenix tests
Posted by Sandhya Sundaresan <sa...@esgyn.com>.
Hi Weishiun,
Yes there is a JIRA for this. JIRA TRAFODION-1825 . Arvind filed that and I
did talk to Anoop briefly about it. There was a suspicion it was checkin for
JIRA 1807. I think we need to see the exact query/string getting to SQL
upsert statement to proceed further on this since the core does not show
any datetime function.
Arvind, if you can provide that to Anoop and me, we can go from there.
Sandhya
-----Original Message-----
From: Wei-Shiun Tsai [mailto:wei-shiun.tsai@esgyn.com]
Sent: Wednesday, February 17, 2016 6:34 PM
To: dev@trafodion.incubator.apache.org
Subject: Mxosrvr cores from phoenix tests
Hi,
Has anybody looked into the cores mentioned by Steve below? At some point,
a regression has started to fail phoenix tests with mxosrvr cores in our
build. I narrowed it down to a smaller java problem to reproduce it. It is
an upsert statement that has caused it. This seems to only happen with JDBC
though. I didn't see this problem when running the same statements in
sqlci. Anyone wants to take a look?
conn.createStatement().execute("create table DescColumnSortOrderTest
(id integer not null, date1 date not null, constraint pk primary key (id
desc, date1));");
pStmt = conn.prepareStatement("upsert into DescColumnSortOrderTest
(id, date1) values (?, ?)");
Object[][] rows = new Object[][]{{1, date(1, 1, 2012)}, {3, date(1, 1,
2013)}, {2, date(1, 1, 2011)}};
for (int row = 0; row < rows.length; row++) {
for (int col = 0; col < rows[row].length; col++) {
Object value = rows[row][col];
pStmt.setObject(col + 1, value);
}
pStmt.execute();
}
Thanks,
Weishiun
-----Original Message-----
From: Steve Varnau [mailto:steve.varnau@esgyn.com]
Sent: Tuesday, February 16, 2016 3:30 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Trafodion master Daily Test Result - 117
After multiple attempts to get the permissions and environment right, I've
finally got the automation generating the back-trace on the corefiles being
generated in the phoenix-part1 tests. Here is one:
http://traf-testlogs.esgyn.com/Daily-master/117/phoenix_part1_T4-hdp-2/corefiles.log
The other test jobs should be covered in tonight's build, though likely the
same results as this one.
--Steve
> -----Original Message-----
> From: steve.varnau@esgyn.com [mailto:steve.varnau@esgyn.com]
> Sent: Tuesday, February 16, 2016 2:54 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Trafodion master Daily Test Result - 117
>
> Daily Automated Testing master
>
> Jenkins Job: https://jenkins.esgyn.com/job/Check-Daily-master/117/
> Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/117
> Bld Downloads: http://traf-builds.esgyn.com
>
> Changes since previous daily build:
> No changes
>
>
> Test Job Results:
>
> FAILURE core-regress-executor-cdh (2 hr 20 min) FAILURE
> core-regress-hive-cdh (46 min) FAILURE core-regress-hive-hdp (39 min)
> FAILURE phoenix_part1_T2-cdh (1 hr 19 min) FAILURE
> phoenix_part1_T2-hdp (1 hr 21 min) FAILURE phoenix_part1_T4-cdh (37
> min) FAILURE phoenix_part1_T4-hdp (1 hr 10 min) SUCCESS
> build-master-debug (30 min) SUCCESS build-master-release (35 min)
> SUCCESS core-regress-charsets-cdh (21 min) SUCCESS
> core-regress-charsets-hdp (1 hr 3 min) SUCCESS
> core-regress-compGeneral-cdh (33 min) SUCCESS
> core-regress-compGeneral-hdp (44 min) SUCCESS core-regress-core-cdh
> (38 min) SUCCESS core-regress-core-hdp (1 hr 20 min) SUCCESS
> core-regress-executor-hdp (54 min) SUCCESS core-regress-fullstack2-cdh
> (48 min) SUCCESS core-regress-fullstack2-hdp (47 min) SUCCESS
> core-regress-privs1-cdh (21 min) SUCCESS core-regress-privs1-hdp (1 hr
> 6 min) SUCCESS core-regress-privs2-cdh (27 min) SUCCESS
> core-regress-privs2-hdp (32 min) SUCCESS core-regress-qat-cdh (13 min)
> SUCCESS core-regress-qat-hdp (18 min) SUCCESS core-regress-seabase-cdh
> (1 hr 20 min) SUCCESS core-regress-seabase-hdp (43 min) SUCCESS
> core-regress-udr-cdh (51 min) SUCCESS core-regress-udr-hdp (18 min)
> SUCCESS jdbc_test-cdh (27 min) SUCCESS jdbc_test-hdp (29 min) SUCCESS
> phoenix_part2_T2-cdh (1 hr 21 min) SUCCESS phoenix_part2_T2-hdp (53
> min) SUCCESS phoenix_part2_T4-cdh (1 hr 9 min) SUCCESS
> phoenix_part2_T4-hdp (42 min) SUCCESS pyodbc_test-cdh (8 min 56 sec)
> SUCCESS pyodbc_test-hdp (43 min)