[Monetdb-developers] [Fabian.Groffen@cwi.nl: Re: [Monetdb-checkins] clients/src/odbc/samples/Tests All, 1.1, NONE odbcsample1.SQL, 1.1, NONE odbcsample1.SQL.bat, 1.1, NONE?odbcsample1.stable.err, 1.1, NONE odbcsample1.stable.out, 1.1, NONE]
This should have been sent to monetdb-developers immediately...
----- Forwarded message from Fabian Groffen Fabian.Groffen@cwi.nl -----
From: Fabian Groffen Fabian.Groffen@cwi.nl To: monetdb-checkins@lists.sourceforge.net Reply-To: monetdb-developers@lists.sourceforge.net Subject: Re: [Monetdb-checkins] clients/src/odbc/samples/Tests All, 1.1, NONE odbcsample1.SQL, 1.1, NONE odbcsample1.SQL.bat, 1.1, NONE odbcsample1.stable.err, 1.1, NONE odbcsample1.stable.out, 1.1, NONE Date: Thu, 11 Jan 2007 16:18:26 +0100 User-Agent: Mutt/1.5.13 (Darwin 8.8.0, VIM - Vi IMproved 7.0) List-Id: "Checkin messages for MonetDB." <monetdb-checkins.lists.sourceforge.net>
On 11-01-2007 15:11:58 +0000, Stefan Manegold wrote:
Update of /cvsroot/monetdb/clients/src/odbc/samples/Tests In directory sc8-pr-cvs7.sourceforge.net:/tmp/cvs-serv12179
Removed Files: All odbcsample1.SQL odbcsample1.SQL.bat odbcsample1.stable.err odbcsample1.stable.out Log Message:
ODBC tests can only be run once we have MonetDB[45] and sql; hence, we remove tests from clients, and revive them in sql/src/odbc/samples/Tests/
Since this seems to me like a problem for many (if not all), I'd like to have a (short) discussion on this first.
Possible other solutions: 1) create a "test" repo, which holds all tests, and make sure we have structure that is able to track the proper dependencies for each test. 2) move all tests to one of the repos where they could be executed (like this commit suggests). Problem is for tests that like to access more languages, or backends. Should they be in multiple places, or is some half-.... dependency tracking necessary anyway? Separates source from tests as well as 1) but in a more fragmented way. 3) don't test. 4) only run testing after all components have been compiled. 5) ???
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ Monetdb-checkins mailing list Monetdb-checkins@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-checkins
----- End forwarded message -----
For the time being, I vote for reviving the odbc and java/jdbc tests in sql (as I did and am doing). A general re-organization of tests might be a good idea, but should be planned carefully --- maybe only after the upcoming release...
Stefan
On Thu, Jan 11, 2007 at 04:19:46PM +0100, Fabian Groffen wrote:
This should have been sent to monetdb-developers immediately...
----- Forwarded message from Fabian Groffen Fabian.Groffen@cwi.nl -----
From: Fabian Groffen Fabian.Groffen@cwi.nl To: monetdb-checkins@lists.sourceforge.net Reply-To: monetdb-developers@lists.sourceforge.net Subject: * Re: [Monetdb-checkins] clients/src/odbc/samples/Tests All, 1.1, NONE odbcsample1.SQL, 1.1, NONE odbcsample1.SQL.bat, 1.1, NONE odbcsample1.stable.err, 1.1, NONE odbcsample1.stable.out, 1.1, NONE Date: Thu, 11 Jan 2007 16:18:26 +0100 User-Agent: Mutt/1.5.13 (Darwin 8.8.0, VIM - Vi IMproved 7.0) List-Id: "Checkin messages for MonetDB." <monetdb-checkins.lists.sourceforge.net>
On 11-01-2007 15:11:58 +0000, Stefan Manegold wrote:
Update of /cvsroot/monetdb/clients/src/odbc/samples/Tests In directory sc8-pr-cvs7.sourceforge.net:/tmp/cvs-serv12179
Removed Files: All odbcsample1.SQL odbcsample1.SQL.bat odbcsample1.stable.err odbcsample1.stable.out Log Message:
ODBC tests can only be run once we have MonetDB[45] and sql; hence, we remove tests from clients, and revive them in sql/src/odbc/samples/Tests/
Since this seems to me like a problem for many (if not all), I'd like to have a (short) discussion on this first.
Possible other solutions:
- create a "test" repo, which holds all tests, and make sure we have structure that is able to track the proper dependencies for each test.
- move all tests to one of the repos where they could be executed (like this commit suggests). Problem is for tests that like to access more languages, or backends. Should they be in multiple places, or is some half-.... dependency tracking necessary anyway? Separates source from tests as well as 1) but in a more fragmented way.
- don't test.
- only run testing after all components have been compiled.
- ???
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ Monetdb-checkins mailing list Monetdb-checkins@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-checkins
----- End forwarded message -----
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
On 11-01-2007 16:55:16 +0100, Stefan Manegold wrote:
For the time being, I vote for reviving the odbc and java/jdbc tests in sql (as I did and am doing).
I think this is a bad idea, and it should not be done.
On Thu, Jan 11, 2007 at 04:59:13PM +0100, Fabian Groffen wrote:
On 11-01-2007 16:55:16 +0100, Stefan Manegold wrote:
For the time being, I vote for reviving the odbc and java/jdbc tests in sql (as I did and am doing).
I think this is a bad idea, and it should not be done.
well, for now I think having the MIL tests in MonetDB4, the MAL tests in MonetDB5 the SQL tests in sql, the XQuery tests in pathfinder is a reasonably good idea.
the sample programs that are used by these tests --- no matter whether they are written in C or java, and no matter whether they use plain MAPI, ODBC or JDBC stay where they belong, i.e., in clients.
independend of that, how (if at all???) can I run the JDBC tests in case the respective jar and programs have already been built, i.e., without using ant; i.e., how do I have to modify (e.g.)
======== $ cat sql/src/jdbc/tests/Tests/Test_Cautocommit.SQL -------- #!/bin/sh
URL="jdbc:monetdb://${HOST}:${MAPIPORT}/${TSTDB}?user=monetdb&password=monetdb${JDBC_EXTRA_ARGS}"
Mlog -x "ant -emacs -buildfile ${TSTSRCDIR}/../build.xml -Dbuilddir=${TSTBLDDIR}/../ -Djdbc_url="${URL}" -Djardir=${TSTBLDDIR}/../../ ${TST}" ========
to do something usefull, in case I have only the above script and
======== $ l `monetdb-clients-config --pkgdatadir`/lib -------- total 200 drwxr-s--- 2 manegold ins1 4096 Jan 10 23:15 ./ drwxr-s--- 7 manegold ins1 4096 Jan 10 23:15 ../ -rwxr-xr-x 1 manegold ins1 110587 Jan 10 23:15 jdbcclient-1.5.jar* -rwxr-xr-x 1 manegold ins1 76159 Jan 10 23:15 monetdb-1.5-jdbc.jar* ======== $ l `monetdb-clients-config --pkgdatadir`/Tests -------- total 56 drwxr-s--- 2 manegold ins1 4096 Jan 10 23:15 ./ drwxr-s--- 7 manegold ins1 4096 Jan 10 23:15 ../ -rwxr-xr-x 1 manegold ins1 2045 Jan 10 23:15 Test_Cautocommit.class* -rwxr-xr-x 1 manegold ins1 1520 Jan 10 23:15 Test_Cmanycon.class* -rwxr-xr-x 1 manegold ins1 3184 Jan 10 23:15 Test_Csavepoints.class* -rwxr-xr-x 1 manegold ins1 2091 Jan 10 23:15 Test_Ctransaction.class* -rwxr-xr-x 1 manegold ins1 3069 Jan 10 23:15 Test_PStimedate.class* -rwxr-xr-x 1 manegold ins1 4298 Jan 10 23:15 Test_Rbooleans.class* -rwxr-xr-x 1 manegold ins1 4232 Jan 10 23:15 Test_Rmetadata.class* -rwxr-xr-x 1 manegold ins1 2275 Jan 10 23:15 Test_Rpositioning.class* -rwxr-xr-x 1 manegold ins1 3676 Jan 10 23:15 Test_Rtimedate.class* -rwxr-xr-x 1 manegold ins1 2442 Jan 10 23:15 Test_Sbatching.class* ========
thanks in advance!
Stefan
On 11-01-2007 19:12:33 +0100, Stefan Manegold wrote:
well, for now I think having the MIL tests in MonetDB4, the MAL tests in MonetDB5 the SQL tests in sql, the XQuery tests in pathfinder is a reasonably good idea.
So, first for some reason you're going to split all repositories into a number of them, to later spaghetti-connect them again, making me wonder why then you didn't merge all repositories into one in the first place.
Fabian Groffen wrote:
On 11-01-2007 19:12:33 +0100, Stefan Manegold wrote:
well, for now I think having the MIL tests in MonetDB4, the MAL tests in MonetDB5 the SQL tests in sql, the XQuery tests in pathfinder is a reasonably good idea.
So, first for some reason you're going to split all repositories into a number of them, to later spaghetti-connect them again, making me wonder why then you didn't merge all repositories into one in the first place.
A split of tests targeted to components is ok, provided you ensure that they address the correct component. For tests using e.g. both MAL/SQL we have to find a solution. Ala, this area should be convenient but not critical at this stage.
participants (3)
-
Fabian Groffen -
Martin Kersten -
Stefan Manegold