Bugs item #1742695, was opened at 2007-06-25 09:54
Message generated for change (Comment added) made by stmane
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1742695&group_id=56967

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: SQL/JDBC
Group: SQL 2.18
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: Stefan Manegold (stmane)
Assigned to: Fabian (mr-meltdown)
Summary: SQL: some JDBC tests fail since 2007/06/04 on some platforms

Initial Comment:
Since Monday June 4 2007, i.e., after checkins on Saturday June 2 2007 and/or 
Sunday une 3 2007 (due to system maintenance at CWI/SARA there was no testing 
on Sunday une 3 2007),
JDBC tests Test_JdbcClient & Test_Sbatching fail with both SQL/4 & SQL/5 on
CentOS4.4 G.32.32.d
RedHat4WS G.64.64.d
SUSE10.2 G.32.32.d

Test_JdbcClient produces extra (unexpected?) output
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d-CentOS4.4/src_jdbc_tests/Test_JdbcClient.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d-RedHat4WS/src_jdbc_tests/Test_JdbcClient.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d-SUSE10.2/src_jdbc_tests/Test_JdbcClient.out.00.html

Test_Sbatching runs into a timeout after 60 seconds (used to finish without 
problems within well below 10 seconds before)
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d-CentOS4.4/src_jdbc_tests/Test_Sbatching.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d-RedHat4WS/src_jdbc_tests/Test_Sbatching.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d-SUSE10.2/src_jdbc_tests/Test_Sbatching.err.00.html


----------------------------------------------------------------------

>Comment By: Stefan Manegold (stmane)
Date: 2007-07-03 11:59

Message:
Logged In: YES 
user_id=572415
Originator: YES

Indeed, the actual problem seems to be a significant (up to factor 10!)
slow-down of test Test_Sbatching:
========
                                                        C4.4    D8.8.0 
D8.9.0  F6      F6      F6      F6      F6      F6      G1.12.9 R4     
S10.2   S5.10
                                                        G32/32d G64/64d
G32/32d G32/32d G64/32d G64/64d G64/64s n64/32d n64/64d G32/32d G64/64d
G32/32d G32/32d
Mtest10..2007.06.01_04-31-24..time
                                       Test_Sbatching    10.440          
8.936   1.992   1.450   1.558   1.385   1.476   1.472   6.225  17.578  
0.465   2.557    Test_Sbatching
Mtest10..2007.06.02_04-21-32..time
                                       Test_Sbatching    10.603          
4.523   1.973   1.457   1.977   1.650   1.672   1.529   6.238  17.847  
0.476   2.283    Test_Sbatching
Mtest10..2007.06.04_00-58-07..time
                                       Test_Sbatching                   
18.343   9.232           5.988                   6.111  19.052  60,387 
60,255  22.413    Test_Sbatching
Mtest10..2007.06.05_00-09-07..time
                                       Test_Sbatching    60,485         
23.277   8.759   6.042   5.987   5.920   6.058   5.767  20.805  60,395 
60,199  22.641    Test_Sbatching
Mtest10..2007.06.06_00-09-08..time
                                       Test_Sbatching    60,465  19.886  
8.811   6.502   6.040   5.965   6.047   5.898  13.847  60,381  60,405 
22.503    Test_Sbatching
                                                        G32/32d G32/32d
G32/32d G64/32d G64/64d G64/64s n64/32d n64/64d G32/32d G64/64d G32/32d
G32/32d
                                                        C4.4    D8.9.0  F6
     F6      F6      F6      F6      F6      G1.12.9 R4      S10.2   S5.10
========

I extended the timeout to 2 mins --- let's see tomorrow, whether this
helps.


----------------------------------------------------------------------

Comment By: Fabian (mr-meltdown)
Date: 2007-07-03 11:30

Message:
Logged In: YES 
user_id=963970
Originator: NO

I cannot find any checkins related to JDBC on Saturday June 2 2007, only
some M5 checkins that seemingly look harmless.
On Sunday june 3 2007 release was prepared/done, so lots of propagation
and version number commits that don't feel like they can be the cause of
action.

Unfortunately I don't have access to the CentOS or SuSE machines that
currently still seem to timeout.  It might be related to the Mtest change
to use hostname instead of localhost again, which routes the traffic over
the interface, and hence aggressive firewalls and real packet
transportation may slow down the actual speed.

----------------------------------------------------------------------

Comment By: Stefan Manegold (stmane)
Date: 2007-06-25 15:14

Message:
Logged In: YES 
user_id=572415
Originator: YES

Some usefull comment from Fabian:

"
I cannot login, so I'll do it this way:

the JdbcClient test fails, because the Sbatching test doesn't clean up
it's mess (because it times out).
"


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1742695&group_id=56967

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs

Reply via email to