[Monetdb-developers] 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (next week)

newer
[Monetdb-developers] what should...

older
[Monetdb-developers] MONET-PHP

Stefan Manegold

4 Nov 2005 4 Nov '05

2:34 p.m.

(some of you might already have see this one coming; cf. http://www.cwi.nl/htbin/cwwwi/agenda?datum=2005_11+dag=09 ;-))

Dear all,

given the success of the 1st MonetDB-Bug-Day on Oct 06 2005,

8 participants managed to check 347 of the then 721 bug reports, added 97 new test scripts, re-opened some bugs that still/again fail and filed 9 new bug reports; see https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... for details,

there will by a 2nd MonetDB-Bug-Day to (hopefully) check the remaining 347 bug reports (plus those filed since Oct 06 2005), and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Wednesday, Nov 9, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 8:00 - 23:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge, and is reasonably familiar with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README).

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.

More detailed instructions can be found at https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... and/or will follow before next Wednesday.

Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the 1st MonetDB-Bug-Day ;-)

Once again thank you very much for your cooperation!

CU next Wednesday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!

Show replies by date

Stefan Manegold

8 Nov 8 Nov

10:18 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

Dear all,

here are some more informations for the 2nd MonetDB-Bug-Day tomorrow.

Please note, though it's call Bug-*Day*, you don't have to spend the whole day writing test scripts (though no one would mind if you did ;-)). Below you find chunks of 10 bug reports each; so simple claim one chunk at a time (by group-reply to this email) whenever you feel like you could spend some minutes on this "community task", check the 10 reports and provide the test script where necessary/applicable. I we don't manage to finish 40 chunks tomorrow, everybody is welcome to pick one any of the next days.

Of course, next to (or instead of) adding test scripts, you're also welcome to fix open bugs (and add the test script for each bug you fix)!

General issues ==============

As with the first MonetDB-Bug-Day, I split the (remaining 391) bug reports in chunks. However, this time, they're smaller --- only 10 instead 50 reports --- to allow more "fine-grained" processing:

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 40 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tomorrow night (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't. (Please see below for details what to do in case your hit a report that requires a test script, but for which you cannot create a test script.)

Requirements ============

Obviously, you need to have MonetDB (plus SQL or XQuery for those bugs) installed and running; preferably an up-to-date ssh-based (non anonymous) CVS check out of either the release branches (MonetDB_4-8, SQL_2-8, XQuery_0-8) or the respective CVS heads. Anonymous (pserver-based) CVS check outs or source distributions should also work, but then you cannot check-in your tests directly (see below on how to participate and submit test script in this case).

Stable vs. Current ------------------

In principle, it does not matter, whether you're using the Stable release branch(es) or the Current development head(s). Use what ever you like best (or have already running).

Test directories ----------------

Your tests must be located (and hence checked in) in different directories depending on the MonetDB version you're using:

Stable branch: MonetDB 4.8.*: MonetDB/tests/BugDay_2005-11-09_4.8/Tests/ SQL 2.8.*: sql/src/test/BugDay_2005-11-09_2.8/Tests/ XQuery 0.8.*: pathfinder/tests/BugDay_2005-11-09_0.8/Tests/

Current head: MonetDB 4.9.3: MonetDB/tests/BugDay_2005-11-09_4.9.3/Tests/ SQL 2.9.3: sql/src/test/BugDay_2005-11-09_2.9.3/Tests/ XQuery 0.9.3: pathfinder/tests/BugDay_2005-11-09_0.9.3/Tests/

The reason for having different directories is mainly convenience with check-ins and later propagations.

Codes =====

To indicate the progress (see below for details), please use the following codes when adding comments to the bug report

code explanation ------------------------+--------------------------------------------- RELEASED / REASSIGN | the "claimer" of the bug wasn't able to create a | script from the bug due to insufficient | knowledge. Append reason, e.g. "XQuery". | Also set status of closed bugs to "pending". ALREADY IN TESTWEB | the script was already in CVS and TestWeb | (added location of existing test script). TEST ADDED / SUCCESS | a script was added (append location & name) and | works correctly. TEST ADDED / FAILURE | a script was added, but it fails (bad output). | Re-open closed bug! TEST SUBMITTED | a script was made, but sent to Stefan (for | non-CVS participants) NO TEST / COMPILATION | no test was added because the bug deals with a | compilation problem. NO TEST / DOCUMENTATION | no test was added because the bug deals with a | documentation issue, or misleading help text, | etc. NO TEST / REDUNDANT | no test was added, because either the bug itself | is a duplicate, or the test that follows out of | the bug would clearly be duplicating another | existing bug. When extending another bug to | remove redundancy use TEST ADDED / SUCCESS and | give the name of the already existing updated | bug.

Note: the last action is only meant for experts in their field ;)

An example message on the SF bug could be:

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS sql/src/tests/bugday/like_join_union.SF-0123345.SQL

The Task/Procedure ==================

Claim a chunk of bugs as described above, and then process each bug as follows:

Checking for existence ----------------------

Once claimed, you first check, whether there is already a test script for this bug (i.e., a test script that contains the respective ID in its filename) available in one of

MonetDB/tests/BugsViaSourgeforce/Tests/ sql/src/test/bugs/Tests/ pathfinder/tests/BugsViaSourgeforce/Tests/

If so, you should indicate this be adding a comment like

BugDay_2005-11-09, <your name>: ALREADY IN TESTWEB MonetDB/tests/BugsViaSourgeforce/Tests/ID.602271.*

to the respective bug report on SF, and you're done with this bug, and can proceed to the next one.

If there is no test script, yet, you need to create one:

Naming conventions ------------------

Names of test scripts must include a descriptive part (of reasonable length) and the SF bug ID, like

"return_types_of_head_and_tail.SF-701641.*",

i.e., the pattern is

<descriptive-name>.SF-<BugID>[.<extension>]

Creating test scripts ---------------------

Most bug reports come with some MIL-, SQL-, XQuery-code, or some other description/instructions how to reproduce the bug. The basic task is to put this into a proper "Mtest-compliant" test script. In most cases, this is just a .milS, .sql, or .xq file. See http://monetdb.cwi.nl/monet/src/testing/README for details about Mtest.py . In case of doubt, please feel free to contact any of your colleagues that might be more familiar with Mtest --- or me of course ;-) Of course, you're welcome to extend the test if appropriate.

In case it is obvious that the bug does not require a test script (e.g., compilation, installation, documentation, or web site bugs), please indicate this by adding a comment like

BugDay_2005-11-09, <your name>: NO TEST / <good reason>

to the respective bug report on SF, and proceed with the next bug.

If a test script is required, but you don't know how to make it (for this particular bug), please feel free to ask for help (or "release" the bug report, again).

Running Mtest -------------

Once you made the test script, you need to run the test. In case you're using `source conf/conf.bash` to setup your MonetDB environment, you can simply call one of

Mtest_MonetDB <descriptive-name>.SF-<BugID> Mtest_sql <descriptive-name>.SF-<BugID> Mtest_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. See `Mtest.py --help` for command line options.

Note: Do NOT change or check-in the "All" file!

This is not required to run tests that are explicitly given on Mtest's command line. I'll will fill the "All" files at the end of the BugDay.

Creating / fixing stable output -------------------------------

After running Mtest, you need to check the output by pointing your browser to the file given at the end of Mtest's console output.

In case the output is correct and as expected, you can approve it by running

Mapprove_MonetDB <descriptive-name>.SF-<BugID> Mapprove_sql <descriptive-name>.SF-<BugID> Mapprove_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. In case running the test failed, please fix the test and start again with running Mtest.

In case the output is not correct or no as expected, you first approve the output as described above, but then edit the files

<descriptive-name>.SF-<BugID>.stable.out <descriptive-name>.SF-<BugID>.stable.err

by hand to create the correct/expected output.

In any case, you then re-run Mtest, and check the output by pointing your browser to the file given at the end of Mtest's console output.

In case everything is "green" (i.e., OK), you can check-in all files related to the test (including the stable output!), indicate the success by adding a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and proceed with the next bug.

In case there is still a red 'X' (because MonetDB does not produce the correct/expected output), you also check-in all files, but indicate the problem by a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / FAILURE tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and *re-open* this bug report, before proceeding with the next bug.

Anonymous CVS check outs and source distributions =================================================

All the above holds, except from the CVS check-in of the new test scripts. Instead, you send me (Stefan.Manegold@cwi.nl) a .tar[.gz] or .zip file including all your new test scripts by the end of your BugDay.

In case you intend to participate without CVS access, please let me know so as soon as you start.

Pooh, I guess that's it for now. I hope, I didn't forget anything --- if so, feel free to ask! (via email, skype, or personally tomorrow at CWI).

cu tomorrow,

Stefan

On Fri, Nov 04, 2005 at 03:34:19PM +0100, Stefan Manegold wrote:

...

(some of you might already have see this one coming; cf. http://www.cwi.nl/htbin/cwwwi/agenda?datum=2005_11+dag=09 ;-))

Dear all,

given the success of the 1st MonetDB-Bug-Day on Oct 06 2005,

8 participants managed to check 347 of the then 721 bug reports, added 97 new test scripts, re-opened some bugs that still/again fail and filed 9 new bug reports; see https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... for details,

there will by a 2nd MonetDB-Bug-Day to (hopefully) check the remaining 347 bug reports (plus those filed since Oct 06 2005), and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Wednesday, Nov 9, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 8:00 - 23:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge, and is reasonably familiar with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README).

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.
    More detailed instructions can be found at 
https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... and/or will follow before next Wednesday.

Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the 1st MonetDB-Bug-Day ;-)

Once again thank you very much for your cooperation!

CU next Wednesday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

Ying (Jennie) Zhang

10:32 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

No Offsets BugIDs # URL

1 213-219 947600- 949071 7 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 2 220-229 949135- 952758 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Dear all,

since the first chunk only contains 7 bugs, I'd like to claim the first two chunks.

Have fun tomorrow.

Jennie

Niels Nes

9 Nov 9 Nov

6:57 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

On Tue, Nov 08, 2005 at 11:18:18PM +0100, Stefan Manegold wrote:

...

Dear all,

here are some more informations for the 2nd MonetDB-Bug-Day tomorrow.

Please note, though it's call Bug-*Day*, you don't have to spend the whole day writing test scripts (though no one would mind if you did ;-)). Below you find chunks of 10 bug reports each; so simple claim one chunk at a time (by group-reply to this email) whenever you feel like you could spend some minutes on this "community task", check the 10 reports and provide the test script where necessary/applicable. I we don't manage to finish 40 chunks tomorrow, everybody is welcome to pick one any of the next days.

Of course, next to (or instead of) adding test scripts, you're also welcome to fix open bugs (and add the test script for each bug you fix)!

General issues

As with the first MonetDB-Bug-Day, I split the (remaining 391) bug reports in chunks. However, this time, they're smaller --- only 10 instead 50 reports --- to allow more "fine-grained" processing:

No Offsets BugIDs # URL

1 213-219 947600- 949071 7 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 2 220-229 949135- 952758 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 3 230-239 953545- 963620 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Okay 3 claimed

Niels

...

4 240-249 963759- 971158 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 5 330-339 1023645-1025005 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 340-349 1025062-1029058 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 350-359 1029099-1034613 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 360-369 1034922-1037591 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 370-379 1037993-1043526 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 380-389 1044534-1063089 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 390-399 1065373-1076344 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 400-409 1076604-1081218 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 13 410-419 1081274-1085120 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 420-429 1085355-1099345 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 430-439 1100291-1113994 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 524-529 1190980-1194362 6 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 530-539 1195753-1201291 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 540-549 1201604-1205010 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 550-559 1205565-1206985 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 24 590-599 1210748-1212707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 25 600-609 1214335-1218268 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 26 610-619 1218281-1227464 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 27 620-629 1227493-1237444 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 28 630-639 1238228-1240701 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 29 640-649 1242164-1256794 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 30 650-659 1257463-1263928 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 31 660-669 1263967-1274649 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 32 670-679 1274819-1281176 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 33 680-689 1281996-1292727 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 34 690-699 1293196-1298707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 35 700-709 1300366-1312972 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 36 710-719 1313008-1314995 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 37 720-729 1315339-1324219 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 38 730-739 1324575-1334486 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 39 740-749 1334536-1347183 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 40 750-757 1347331-1351516 8 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 391

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 40 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tomorrow night (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't. (Please see below for details what to do in case your hit a report that requires a test script, but for which you cannot create a test script.)

Requirements

Obviously, you need to have MonetDB (plus SQL or XQuery for those bugs) installed and running; preferably an up-to-date ssh-based (non anonymous) CVS check out of either the release branches (MonetDB_4-8, SQL_2-8, XQuery_0-8) or the respective CVS heads. Anonymous (pserver-based) CVS check outs or source distributions should also work, but then you cannot check-in your tests directly (see below on how to participate and submit test script in this case).

Stable vs. Current

In principle, it does not matter, whether you're using the Stable release branch(es) or the Current development head(s). Use what ever you like best (or have already running).

Test directories

Your tests must be located (and hence checked in) in different directories depending on the MonetDB version you're using:

Stable branch: MonetDB 4.8.*: MonetDB/tests/BugDay_2005-11-09_4.8/Tests/ SQL 2.8.*: sql/src/test/BugDay_2005-11-09_2.8/Tests/ XQuery 0.8.*: pathfinder/tests/BugDay_2005-11-09_0.8/Tests/

Current head: MonetDB 4.9.3: MonetDB/tests/BugDay_2005-11-09_4.9.3/Tests/ SQL 2.9.3: sql/src/test/BugDay_2005-11-09_2.9.3/Tests/ XQuery 0.9.3: pathfinder/tests/BugDay_2005-11-09_0.9.3/Tests/

The reason for having different directories is mainly convenience with check-ins and later propagations.

Codes

To indicate the progress (see below for details), please use the following codes when adding comments to the bug report

code explanation ------------------------+--------------------------------------------- RELEASED / REASSIGN | the "claimer" of the bug wasn't able to create a | script from the bug due to insufficient | knowledge. Append reason, e.g. "XQuery". | Also set status of closed bugs to "pending". ALREADY IN TESTWEB | the script was already in CVS and TestWeb | (added location of existing test script). TEST ADDED / SUCCESS | a script was added (append location & name) and | works correctly. TEST ADDED / FAILURE | a script was added, but it fails (bad output). | Re-open closed bug! TEST SUBMITTED | a script was made, but sent to Stefan (for | non-CVS participants) NO TEST / COMPILATION | no test was added because the bug deals with a | compilation problem. NO TEST / DOCUMENTATION | no test was added because the bug deals with a | documentation issue, or misleading help text, | etc. NO TEST / REDUNDANT | no test was added, because either the bug itself | is a duplicate, or the test that follows out of | the bug would clearly be duplicating another | existing bug. When extending another bug to | remove redundancy use TEST ADDED / SUCCESS and | give the name of the already existing updated | bug.

Note: the last action is only meant for experts in their field ;)

An example message on the SF bug could be:

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS sql/src/tests/bugday/like_join_union.SF-0123345.SQL

The Task/Procedure

Claim a chunk of bugs as described above, and then process each bug as follows:

Checking for existence

Once claimed, you first check, whether there is already a test script for this bug (i.e., a test script that contains the respective ID in its filename) available in one of

MonetDB/tests/BugsViaSourgeforce/Tests/ sql/src/test/bugs/Tests/ pathfinder/tests/BugsViaSourgeforce/Tests/

If so, you should indicate this be adding a comment like

BugDay_2005-11-09, <your name>: ALREADY IN TESTWEB MonetDB/tests/BugsViaSourgeforce/Tests/ID.602271.*

to the respective bug report on SF, and you're done with this bug, and can proceed to the next one.

If there is no test script, yet, you need to create one:

Naming conventions

Names of test scripts must include a descriptive part (of reasonable length) and the SF bug ID, like

"return_types_of_head_and_tail.SF-701641.*",

i.e., the pattern is

<descriptive-name>.SF-<BugID>[.<extension>]

Creating test scripts

Most bug reports come with some MIL-, SQL-, XQuery-code, or some other description/instructions how to reproduce the bug. The basic task is to put this into a proper "Mtest-compliant" test script. In most cases, this is just a .milS, .sql, or .xq file. See http://monetdb.cwi.nl/monet/src/testing/README for details about Mtest.py . In case of doubt, please feel free to contact any of your colleagues that might be more familiar with Mtest --- or me of course ;-) Of course, you're welcome to extend the test if appropriate.

In case it is obvious that the bug does not require a test script (e.g., compilation, installation, documentation, or web site bugs), please indicate this by adding a comment like

BugDay_2005-11-09, <your name>: NO TEST / <good reason>

to the respective bug report on SF, and proceed with the next bug.

If a test script is required, but you don't know how to make it (for this particular bug), please feel free to ask for help (or "release" the bug report, again).

Running Mtest

Once you made the test script, you need to run the test. In case you're using `source conf/conf.bash` to setup your MonetDB environment, you can simply call one of

Mtest_MonetDB <descriptive-name>.SF-<BugID> Mtest_sql <descriptive-name>.SF-<BugID> Mtest_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. See `Mtest.py --help` for command line options.

Note: Do NOT change or check-in the "All" file!

This is not required to run tests that are explicitly given on Mtest's command line. I'll will fill the "All" files at the end of the BugDay.

Creating / fixing stable output

After running Mtest, you need to check the output by pointing your browser to the file given at the end of Mtest's console output.

In case the output is correct and as expected, you can approve it by running

Mapprove_MonetDB <descriptive-name>.SF-<BugID> Mapprove_sql <descriptive-name>.SF-<BugID> Mapprove_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above.

In case running the test failed, please fix the test and start again with running Mtest.

In case the output is not correct or no as expected, you first approve the output as described above, but then edit the files

<descriptive-name>.SF-<BugID>.stable.out <descriptive-name>.SF-<BugID>.stable.err

by hand to create the correct/expected output.

In any case, you then re-run Mtest, and check the output by pointing your browser to the file given at the end of Mtest's console output.

In case everything is "green" (i.e., OK), you can check-in all files related to the test (including the stable output!), indicate the success by adding a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and proceed with the next bug.

In case there is still a red 'X' (because MonetDB does not produce the correct/expected output), you also check-in all files, but indicate the problem by a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / FAILURE tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

<possibly a description of the failure>

to the respective bug report on SF, and *re-open* this bug report, before proceeding with the next bug.

Anonymous CVS check outs and source distributions

All the above holds, except from the CVS check-in of the new test scripts. Instead, you send me (Stefan.Manegold@cwi.nl) a .tar[.gz] or .zip file including all your new test scripts by the end of your BugDay.

In case you intend to participate without CVS access, please let me know so as soon as you start.

Pooh, I guess that's it for now. I hope, I didn't forget anything --- if so, feel free to ask! (via email, skype, or personally tomorrow at CWI).

cu tomorrow,

Stefan

On Fri, Nov 04, 2005 at 03:34:19PM +0100, Stefan Manegold wrote:

...
(some of you might already have see this one coming; cf. http://www.cwi.nl/htbin/cwwwi/agenda?datum=2005_11+dag=09 ;-))

Dear all,

given the success of the 1st MonetDB-Bug-Day on Oct 06 2005,

8 participants managed to check 347 of the then 721 bug reports, added 97 new test scripts, re-opened some bugs that still/again fail and filed 9 new bug reports; see https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... for details,

there will by a 2nd MonetDB-Bug-Day to (hopefully) check the remaining 347 bug reports (plus those filed since Oct 06 2005), and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Wednesday, Nov 9, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 8:00 - 23:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge, and is reasonably familiar with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README).

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.
    More detailed instructions can be found at 
https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... and/or will follow before next Wednesday.

Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the 1st MonetDB-Bug-Day ;-)

Once again thank you very much for your cooperation!

CU next Wednesday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

-- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl

Niels Nes

7:43 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

On Tue, Nov 08, 2005 at 11:18:18PM +0100, Stefan Manegold wrote:

...

Dear all,

here are some more informations for the 2nd MonetDB-Bug-Day tomorrow.

Please note, though it's call Bug-*Day*, you don't have to spend the whole day writing test scripts (though no one would mind if you did ;-)). Below you find chunks of 10 bug reports each; so simple claim one chunk at a time (by group-reply to this email) whenever you feel like you could spend some minutes on this "community task", check the 10 reports and provide the test script where necessary/applicable. I we don't manage to finish 40 chunks tomorrow, everybody is welcome to pick one any of the next days.

Of course, next to (or instead of) adding test scripts, you're also welcome to fix open bugs (and add the test script for each bug you fix)!

General issues

As with the first MonetDB-Bug-Day, I split the (remaining 391) bug reports in chunks. However, this time, they're smaller --- only 10 instead 50 reports --- to allow more "fine-grained" processing:

No Offsets BugIDs # URL

1 213-219 947600- 949071 7 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 2 220-229 949135- 952758 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 3 230-239 953545- 963620 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 4 240-249 963759- 971158 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Finished 3 so moving on to 4

Niels

...

5 330-339 1023645-1025005 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 340-349 1025062-1029058 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 350-359 1029099-1034613 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 360-369 1034922-1037591 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 370-379 1037993-1043526 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 380-389 1044534-1063089 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 390-399 1065373-1076344 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 400-409 1076604-1081218 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 13 410-419 1081274-1085120 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 420-429 1085355-1099345 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 430-439 1100291-1113994 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 524-529 1190980-1194362 6 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 530-539 1195753-1201291 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 540-549 1201604-1205010 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 550-559 1205565-1206985 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 24 590-599 1210748-1212707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 25 600-609 1214335-1218268 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 26 610-619 1218281-1227464 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 27 620-629 1227493-1237444 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 28 630-639 1238228-1240701 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 29 640-649 1242164-1256794 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 30 650-659 1257463-1263928 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 31 660-669 1263967-1274649 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 32 670-679 1274819-1281176 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 33 680-689 1281996-1292727 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 34 690-699 1293196-1298707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 35 700-709 1300366-1312972 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 36 710-719 1313008-1314995 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 37 720-729 1315339-1324219 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 38 730-739 1324575-1334486 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 39 740-749 1334536-1347183 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 40 750-757 1347331-1351516 8 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 391

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 40 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tomorrow night (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't. (Please see below for details what to do in case your hit a report that requires a test script, but for which you cannot create a test script.)

Requirements

Obviously, you need to have MonetDB (plus SQL or XQuery for those bugs) installed and running; preferably an up-to-date ssh-based (non anonymous) CVS check out of either the release branches (MonetDB_4-8, SQL_2-8, XQuery_0-8) or the respective CVS heads. Anonymous (pserver-based) CVS check outs or source distributions should also work, but then you cannot check-in your tests directly (see below on how to participate and submit test script in this case).

Stable vs. Current

In principle, it does not matter, whether you're using the Stable release branch(es) or the Current development head(s). Use what ever you like best (or have already running).

Test directories

Your tests must be located (and hence checked in) in different directories depending on the MonetDB version you're using:

Stable branch: MonetDB 4.8.*: MonetDB/tests/BugDay_2005-11-09_4.8/Tests/ SQL 2.8.*: sql/src/test/BugDay_2005-11-09_2.8/Tests/ XQuery 0.8.*: pathfinder/tests/BugDay_2005-11-09_0.8/Tests/

Current head: MonetDB 4.9.3: MonetDB/tests/BugDay_2005-11-09_4.9.3/Tests/ SQL 2.9.3: sql/src/test/BugDay_2005-11-09_2.9.3/Tests/ XQuery 0.9.3: pathfinder/tests/BugDay_2005-11-09_0.9.3/Tests/

The reason for having different directories is mainly convenience with check-ins and later propagations.

Codes

To indicate the progress (see below for details), please use the following codes when adding comments to the bug report

code explanation ------------------------+--------------------------------------------- RELEASED / REASSIGN | the "claimer" of the bug wasn't able to create a | script from the bug due to insufficient | knowledge. Append reason, e.g. "XQuery". | Also set status of closed bugs to "pending". ALREADY IN TESTWEB | the script was already in CVS and TestWeb | (added location of existing test script). TEST ADDED / SUCCESS | a script was added (append location & name) and | works correctly. TEST ADDED / FAILURE | a script was added, but it fails (bad output). | Re-open closed bug! TEST SUBMITTED | a script was made, but sent to Stefan (for | non-CVS participants) NO TEST / COMPILATION | no test was added because the bug deals with a | compilation problem. NO TEST / DOCUMENTATION | no test was added because the bug deals with a | documentation issue, or misleading help text, | etc. NO TEST / REDUNDANT | no test was added, because either the bug itself | is a duplicate, or the test that follows out of | the bug would clearly be duplicating another | existing bug. When extending another bug to | remove redundancy use TEST ADDED / SUCCESS and | give the name of the already existing updated | bug.

Note: the last action is only meant for experts in their field ;)

An example message on the SF bug could be:

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS sql/src/tests/bugday/like_join_union.SF-0123345.SQL

The Task/Procedure

Claim a chunk of bugs as described above, and then process each bug as follows:

Checking for existence

Once claimed, you first check, whether there is already a test script for this bug (i.e., a test script that contains the respective ID in its filename) available in one of

MonetDB/tests/BugsViaSourgeforce/Tests/ sql/src/test/bugs/Tests/ pathfinder/tests/BugsViaSourgeforce/Tests/

If so, you should indicate this be adding a comment like

BugDay_2005-11-09, <your name>: ALREADY IN TESTWEB MonetDB/tests/BugsViaSourgeforce/Tests/ID.602271.*

to the respective bug report on SF, and you're done with this bug, and can proceed to the next one.

If there is no test script, yet, you need to create one:

Naming conventions

Names of test scripts must include a descriptive part (of reasonable length) and the SF bug ID, like

"return_types_of_head_and_tail.SF-701641.*",

i.e., the pattern is

<descriptive-name>.SF-<BugID>[.<extension>]

Creating test scripts

Most bug reports come with some MIL-, SQL-, XQuery-code, or some other description/instructions how to reproduce the bug. The basic task is to put this into a proper "Mtest-compliant" test script. In most cases, this is just a .milS, .sql, or .xq file. See http://monetdb.cwi.nl/monet/src/testing/README for details about Mtest.py . In case of doubt, please feel free to contact any of your colleagues that might be more familiar with Mtest --- or me of course ;-) Of course, you're welcome to extend the test if appropriate.

In case it is obvious that the bug does not require a test script (e.g., compilation, installation, documentation, or web site bugs), please indicate this by adding a comment like

BugDay_2005-11-09, <your name>: NO TEST / <good reason>

to the respective bug report on SF, and proceed with the next bug.

If a test script is required, but you don't know how to make it (for this particular bug), please feel free to ask for help (or "release" the bug report, again).

Running Mtest

Once you made the test script, you need to run the test. In case you're using `source conf/conf.bash` to setup your MonetDB environment, you can simply call one of

Mtest_MonetDB <descriptive-name>.SF-<BugID> Mtest_sql <descriptive-name>.SF-<BugID> Mtest_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. See `Mtest.py --help` for command line options.

Note: Do NOT change or check-in the "All" file!

This is not required to run tests that are explicitly given on Mtest's command line. I'll will fill the "All" files at the end of the BugDay.

Creating / fixing stable output

After running Mtest, you need to check the output by pointing your browser to the file given at the end of Mtest's console output.

In case the output is correct and as expected, you can approve it by running

Mapprove_MonetDB <descriptive-name>.SF-<BugID> Mapprove_sql <descriptive-name>.SF-<BugID> Mapprove_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above.

In case running the test failed, please fix the test and start again with running Mtest.

In case the output is not correct or no as expected, you first approve the output as described above, but then edit the files

<descriptive-name>.SF-<BugID>.stable.out <descriptive-name>.SF-<BugID>.stable.err

by hand to create the correct/expected output.

In any case, you then re-run Mtest, and check the output by pointing your browser to the file given at the end of Mtest's console output.

In case everything is "green" (i.e., OK), you can check-in all files related to the test (including the stable output!), indicate the success by adding a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and proceed with the next bug.

In case there is still a red 'X' (because MonetDB does not produce the correct/expected output), you also check-in all files, but indicate the problem by a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / FAILURE tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

<possibly a description of the failure>

to the respective bug report on SF, and *re-open* this bug report, before proceeding with the next bug.

Anonymous CVS check outs and source distributions

All the above holds, except from the CVS check-in of the new test scripts. Instead, you send me (Stefan.Manegold@cwi.nl) a .tar[.gz] or .zip file including all your new test scripts by the end of your BugDay.

In case you intend to participate without CVS access, please let me know so as soon as you start.

Pooh, I guess that's it for now. I hope, I didn't forget anything --- if so, feel free to ask! (via email, skype, or personally tomorrow at CWI).

cu tomorrow,

Stefan

On Fri, Nov 04, 2005 at 03:34:19PM +0100, Stefan Manegold wrote:

...
(some of you might already have see this one coming; cf. http://www.cwi.nl/htbin/cwwwi/agenda?datum=2005_11+dag=09 ;-))

Dear all,

given the success of the 1st MonetDB-Bug-Day on Oct 06 2005,

8 participants managed to check 347 of the then 721 bug reports, added 97 new test scripts, re-opened some bugs that still/again fail and filed 9 new bug reports; see https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... for details,

there will by a 2nd MonetDB-Bug-Day to (hopefully) check the remaining 347 bug reports (plus those filed since Oct 06 2005), and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Wednesday, Nov 9, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 8:00 - 23:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge, and is reasonably familiar with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README).

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.
    More detailed instructions can be found at 
https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... and/or will follow before next Wednesday.

Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the 1st MonetDB-Bug-Day ;-)

Once again thank you very much for your cooperation!

CU next Wednesday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

Stefan Manegold

8:39 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

...
As with the first MonetDB-Bug-Day, I split the (remaining 391) bug reports in chunks. However, this time, they're smaller --- only 10 instead 50 reports --- to allow more "fine-grained" processing:

No Offsets BugIDs # URL

1 213-219 947600- 949071 7 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 2 220-229 949135- 952758 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 3 230-239 953545- 963620 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 4 240-249 963759- 971158 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Finished 3 so moving on to 4

Niels

...
5 330-339 1023645-1025005 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

5 is for me, then.

Stefan

...

...
6 340-349 1025062-1029058 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 350-359 1029099-1034613 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 360-369 1034922-1037591 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 370-379 1037993-1043526 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 380-389 1044534-1063089 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 390-399 1065373-1076344 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 400-409 1076604-1081218 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 13 410-419 1081274-1085120 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 420-429 1085355-1099345 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 430-439 1100291-1113994 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 524-529 1190980-1194362 6 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 530-539 1195753-1201291 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 540-549 1201604-1205010 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 550-559 1205565-1206985 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 24 590-599 1210748-1212707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 25 600-609 1214335-1218268 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 26 610-619 1218281-1227464 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 27 620-629 1227493-1237444 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 28 630-639 1238228-1240701 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 29 640-649 1242164-1256794 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 30 650-659 1257463-1263928 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 31 660-669 1263967-1274649 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 32 670-679 1274819-1281176 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 33 680-689 1281996-1292727 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 34 690-699 1293196-1298707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 35 700-709 1300366-1312972 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 36 710-719 1313008-1314995 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 37 720-729 1315339-1324219 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 38 730-739 1324575-1334486 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 39 740-749 1334536-1347183 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 40 750-757 1347331-1351516 8 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 391

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 40 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tomorrow night (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't.

Wouter Alink (CWI)

10:39 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

Hello! I'm in... taking batch 11

Grtz, Wouter

11 390-399 1065373-1076344 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

...

...

Stefan Manegold wrote:

...

...
...
As with the first MonetDB-Bug-Day, I split the (remaining 391) bug reports in chunks. However, this time, they're smaller --- only 10 instead 50 reports --- to allow more "fine-grained" processing:

No Offsets BugIDs # URL

1 213-219 947600- 949071 7 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 2 220-229 949135- 952758 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 3 230-239 953545- 963620 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 4 240-249 963759- 971158 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Finished 3 so moving on to 4

Niels

...
5 330-339 1023645-1025005 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

5 is for me, then.

Stefan

...
...
6 340-349 1025062-1029058 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 350-359 1029099-1034613 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 360-369 1034922-1037591 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 370-379 1037993-1043526 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 380-389 1044534-1063089 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 390-399 1065373-1076344 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 400-409 1076604-1081218 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 13 410-419 1081274-1085120 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 420-429 1085355-1099345 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 430-439 1100291-1113994 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 524-529 1190980-1194362 6 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 530-539 1195753-1201291 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 540-549 1201604-1205010 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 550-559 1205565-1206985 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 24 590-599 1210748-1212707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 25 600-609 1214335-1218268 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 26 610-619 1218281-1227464 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 27 620-629 1227493-1237444 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 28 630-639 1238228-1240701 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 29 640-649 1242164-1256794 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 30 650-659 1257463-1263928 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 31 660-669 1263967-1274649 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 32 670-679 1274819-1281176 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 33 680-689 1281996-1292727 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 34 690-699 1293196-1298707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 35 700-709 1300366-1312972 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 36 710-719 1313008-1314995 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 37 720-729 1315339-1324219 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 38 730-739 1324575-1334486 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 39 740-749 1334536-1347183 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 40 750-757 1347331-1351516 8 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 391

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 40 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tomorrow night (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't.

Sjoerd Mullender

9:13 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

Stefan Manegold wrote:

...

No Offsets BugIDs # URL

...

6 340-349 1025062-1029058 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

This one is mine.

-- Sjoerd Mullender

Niels Nes

9:25 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

On Tue, Nov 08, 2005 at 11:18:18PM +0100, Stefan Manegold wrote:

...

Dear all,

here are some more informations for the 2nd MonetDB-Bug-Day tomorrow.

Please note, though it's call Bug-*Day*, you don't have to spend the whole day writing test scripts (though no one would mind if you did ;-)). Below you find chunks of 10 bug reports each; so simple claim one chunk at a time (by group-reply to this email) whenever you feel like you could spend some minutes on this "community task", check the 10 reports and provide the test script where necessary/applicable. I we don't manage to finish 40 chunks tomorrow, everybody is welcome to pick one any of the next days.

Of course, next to (or instead of) adding test scripts, you're also welcome to fix open bugs (and add the test script for each bug you fix)!

General issues

As with the first MonetDB-Bug-Day, I split the (remaining 391) bug reports in chunks. However, this time, they're smaller --- only 10 instead 50 reports --- to allow more "fine-grained" processing:

No Offsets BugIDs # URL

1 213-219 947600- 949071 7 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 2 220-229 949135- 952758 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 3 230-239 953545- 963620 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 4 240-249 963759- 971158 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 5 330-339 1023645-1025005 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 340-349 1025062-1029058 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 350-359 1029099-1034613 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

7 is mine

Niels

...

8 360-369 1034922-1037591 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 370-379 1037993-1043526 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 380-389 1044534-1063089 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 390-399 1065373-1076344 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 400-409 1076604-1081218 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 13 410-419 1081274-1085120 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 420-429 1085355-1099345 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 430-439 1100291-1113994 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 524-529 1190980-1194362 6 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 530-539 1195753-1201291 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 540-549 1201604-1205010 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 550-559 1205565-1206985 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 24 590-599 1210748-1212707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 25 600-609 1214335-1218268 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 26 610-619 1218281-1227464 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 27 620-629 1227493-1237444 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 28 630-639 1238228-1240701 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 29 640-649 1242164-1256794 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 30 650-659 1257463-1263928 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 31 660-669 1263967-1274649 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 32 670-679 1274819-1281176 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 33 680-689 1281996-1292727 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 34 690-699 1293196-1298707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 35 700-709 1300366-1312972 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 36 710-719 1313008-1314995 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 37 720-729 1315339-1324219 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 38 730-739 1324575-1334486 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 39 740-749 1334536-1347183 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 40 750-757 1347331-1351516 8 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 391

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 40 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tomorrow night (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't. (Please see below for details what to do in case your hit a report that requires a test script, but for which you cannot create a test script.)

Requirements

Obviously, you need to have MonetDB (plus SQL or XQuery for those bugs) installed and running; preferably an up-to-date ssh-based (non anonymous) CVS check out of either the release branches (MonetDB_4-8, SQL_2-8, XQuery_0-8) or the respective CVS heads. Anonymous (pserver-based) CVS check outs or source distributions should also work, but then you cannot check-in your tests directly (see below on how to participate and submit test script in this case).

Stable vs. Current

In principle, it does not matter, whether you're using the Stable release branch(es) or the Current development head(s). Use what ever you like best (or have already running).

Test directories

Your tests must be located (and hence checked in) in different directories depending on the MonetDB version you're using:

Stable branch: MonetDB 4.8.*: MonetDB/tests/BugDay_2005-11-09_4.8/Tests/ SQL 2.8.*: sql/src/test/BugDay_2005-11-09_2.8/Tests/ XQuery 0.8.*: pathfinder/tests/BugDay_2005-11-09_0.8/Tests/

Current head: MonetDB 4.9.3: MonetDB/tests/BugDay_2005-11-09_4.9.3/Tests/ SQL 2.9.3: sql/src/test/BugDay_2005-11-09_2.9.3/Tests/ XQuery 0.9.3: pathfinder/tests/BugDay_2005-11-09_0.9.3/Tests/

The reason for having different directories is mainly convenience with check-ins and later propagations.

Codes

To indicate the progress (see below for details), please use the following codes when adding comments to the bug report

code explanation ------------------------+--------------------------------------------- RELEASED / REASSIGN | the "claimer" of the bug wasn't able to create a | script from the bug due to insufficient | knowledge. Append reason, e.g. "XQuery". | Also set status of closed bugs to "pending". ALREADY IN TESTWEB | the script was already in CVS and TestWeb | (added location of existing test script). TEST ADDED / SUCCESS | a script was added (append location & name) and | works correctly. TEST ADDED / FAILURE | a script was added, but it fails (bad output). | Re-open closed bug! TEST SUBMITTED | a script was made, but sent to Stefan (for | non-CVS participants) NO TEST / COMPILATION | no test was added because the bug deals with a | compilation problem. NO TEST / DOCUMENTATION | no test was added because the bug deals with a | documentation issue, or misleading help text, | etc. NO TEST / REDUNDANT | no test was added, because either the bug itself | is a duplicate, or the test that follows out of | the bug would clearly be duplicating another | existing bug. When extending another bug to | remove redundancy use TEST ADDED / SUCCESS and | give the name of the already existing updated | bug.

Note: the last action is only meant for experts in their field ;)

An example message on the SF bug could be:

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS sql/src/tests/bugday/like_join_union.SF-0123345.SQL

The Task/Procedure

Claim a chunk of bugs as described above, and then process each bug as follows:

Checking for existence

Once claimed, you first check, whether there is already a test script for this bug (i.e., a test script that contains the respective ID in its filename) available in one of

MonetDB/tests/BugsViaSourgeforce/Tests/ sql/src/test/bugs/Tests/ pathfinder/tests/BugsViaSourgeforce/Tests/

If so, you should indicate this be adding a comment like

BugDay_2005-11-09, <your name>: ALREADY IN TESTWEB MonetDB/tests/BugsViaSourgeforce/Tests/ID.602271.*

to the respective bug report on SF, and you're done with this bug, and can proceed to the next one.

If there is no test script, yet, you need to create one:

Naming conventions

Names of test scripts must include a descriptive part (of reasonable length) and the SF bug ID, like

"return_types_of_head_and_tail.SF-701641.*",

i.e., the pattern is

<descriptive-name>.SF-<BugID>[.<extension>]

Creating test scripts

Most bug reports come with some MIL-, SQL-, XQuery-code, or some other description/instructions how to reproduce the bug. The basic task is to put this into a proper "Mtest-compliant" test script. In most cases, this is just a .milS, .sql, or .xq file. See http://monetdb.cwi.nl/monet/src/testing/README for details about Mtest.py . In case of doubt, please feel free to contact any of your colleagues that might be more familiar with Mtest --- or me of course ;-) Of course, you're welcome to extend the test if appropriate.

In case it is obvious that the bug does not require a test script (e.g., compilation, installation, documentation, or web site bugs), please indicate this by adding a comment like

BugDay_2005-11-09, <your name>: NO TEST / <good reason>

to the respective bug report on SF, and proceed with the next bug.

If a test script is required, but you don't know how to make it (for this particular bug), please feel free to ask for help (or "release" the bug report, again).

Running Mtest

Once you made the test script, you need to run the test. In case you're using `source conf/conf.bash` to setup your MonetDB environment, you can simply call one of

Mtest_MonetDB <descriptive-name>.SF-<BugID> Mtest_sql <descriptive-name>.SF-<BugID> Mtest_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. See `Mtest.py --help` for command line options.

Note: Do NOT change or check-in the "All" file!

This is not required to run tests that are explicitly given on Mtest's command line. I'll will fill the "All" files at the end of the BugDay.

Creating / fixing stable output

After running Mtest, you need to check the output by pointing your browser to the file given at the end of Mtest's console output.

In case the output is correct and as expected, you can approve it by running

Mapprove_MonetDB <descriptive-name>.SF-<BugID> Mapprove_sql <descriptive-name>.SF-<BugID> Mapprove_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above.

In case running the test failed, please fix the test and start again with running Mtest.

In case the output is not correct or no as expected, you first approve the output as described above, but then edit the files

<descriptive-name>.SF-<BugID>.stable.out <descriptive-name>.SF-<BugID>.stable.err

by hand to create the correct/expected output.

In any case, you then re-run Mtest, and check the output by pointing your browser to the file given at the end of Mtest's console output.

In case everything is "green" (i.e., OK), you can check-in all files related to the test (including the stable output!), indicate the success by adding a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and proceed with the next bug.

In case there is still a red 'X' (because MonetDB does not produce the correct/expected output), you also check-in all files, but indicate the problem by a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / FAILURE tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

<possibly a description of the failure>

to the respective bug report on SF, and *re-open* this bug report, before proceeding with the next bug.

Anonymous CVS check outs and source distributions

All the above holds, except from the CVS check-in of the new test scripts. Instead, you send me (Stefan.Manegold@cwi.nl) a .tar[.gz] or .zip file including all your new test scripts by the end of your BugDay.

In case you intend to participate without CVS access, please let me know so as soon as you start.

Pooh, I guess that's it for now. I hope, I didn't forget anything --- if so, feel free to ask! (via email, skype, or personally tomorrow at CWI).

cu tomorrow,

Stefan

On Fri, Nov 04, 2005 at 03:34:19PM +0100, Stefan Manegold wrote:

...
(some of you might already have see this one coming; cf. http://www.cwi.nl/htbin/cwwwi/agenda?datum=2005_11+dag=09 ;-))

Dear all,

given the success of the 1st MonetDB-Bug-Day on Oct 06 2005,

8 participants managed to check 347 of the then 721 bug reports, added 97 new test scripts, re-opened some bugs that still/again fail and filed 9 new bug reports; see https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... for details,

there will by a 2nd MonetDB-Bug-Day to (hopefully) check the remaining 347 bug reports (plus those filed since Oct 06 2005), and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Wednesday, Nov 9, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 8:00 - 23:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge, and is reasonably familiar with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README).

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.
    More detailed instructions can be found at 
https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... and/or will follow before next Wednesday.

Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the 1st MonetDB-Bug-Day ;-)

Once again thank you very much for your cooperation!

CU next Wednesday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

Stefan Manegold

9:52 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

...
No Offsets BugIDs # URL

8 360-369 1034922-1037591 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

I'll proceed with 8

Stefan

...

...
9 370-379 1037993-1043526 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 380-389 1044534-1063089 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 390-399 1065373-1076344 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 400-409 1076604-1081218 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 13 410-419 1081274-1085120 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 420-429 1085355-1099345 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 430-439 1100291-1113994 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 524-529 1190980-1194362 6 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 530-539 1195753-1201291 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 540-549 1201604-1205010 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 550-559 1205565-1206985 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 24 590-599 1210748-1212707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 25 600-609 1214335-1218268 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 26 610-619 1218281-1227464 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 27 620-629 1227493-1237444 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 28 630-639 1238228-1240701 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 29 640-649 1242164-1256794 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 30 650-659 1257463-1263928 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 31 660-669 1263967-1274649 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 32 670-679 1274819-1281176 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 33 680-689 1281996-1292727 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 34 690-699 1293196-1298707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 35 700-709 1300366-1312972 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 36 710-719 1313008-1314995 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 37 720-729 1315339-1324219 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 38 730-739 1324575-1334486 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 39 740-749 1334536-1347183 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 40 750-757 1347331-1351516 8 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 391

Niels Nes

10:20 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

On Tue, Nov 08, 2005 at 11:18:18PM +0100, Stefan Manegold wrote:

...

9 370-379 1037993-1043526 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

is mine

Fabian Groffen

10:30 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

On 08-11-2005 23:18:18 +0100, Stefan Manegold wrote:

...

10 380-389 1044534-1063089 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Will embrace these ones

Ying (Jennie) Zhang

11:36 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

12 400-409 1076604-1081218 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Take chunk nr 12

Sjoerd Mullender

11:42 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

13 410-419 1081274-1085120 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Mine.

-- Sjoerd Mullender

Stefan Manegold

11:45 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

14 420-429 1085355-1099345 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

14 is my next chunk.

Stefan

Niels Nes

11:58 a.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

15 430-439 1100291-1113994 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Mine...

Niels

Martin Kersten

12:39 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

Stefan Manegold wrote:

...

Dear all,

here are some more informations for the 2nd MonetDB-Bug-Day tomorrow.

Please note, though it's call Bug-*Day*, you don't have to spend the whole day writing test scripts (though no one would mind if you did ;-)). Below you find chunks of 10 bug reports each; so simple claim one chunk at a time (by group-reply to this email) whenever you feel like you could spend some minutes on this "community task", check the 10 reports and provide the test script where necessary/applicable. I we don't manage to finish 40 chunks tomorrow, everybody is welcome to pick one any of the next days.

Of course, next to (or instead of) adding test scripts, you're also welcome to fix open bugs (and add the test script for each bug you fix)!

General issues

As with the first MonetDB-Bug-Day, I split the (remaining 391) bug reports in chunks. However, this time, they're smaller --- only 10 instead 50 reports --- to allow more "fine-grained" processing:

No Offsets BugIDs # URL

1 213-219 947600- 949071 7 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 2 220-229 949135- 952758 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 3 230-239 953545- 963620 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 4 240-249 963759- 971158 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 5 330-339 1023645-1025005 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 340-349 1025062-1029058 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 350-359 1029099-1034613 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 360-369 1034922-1037591 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 370-379 1037993-1043526 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 380-389 1044534-1063089 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 390-399 1065373-1076344 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 400-409 1076604-1081218 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 13 410-419 1081274-1085120 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 420-429 1085355-1099345 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 430-439 1100291-1113994 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 524-529 1190980-1194362 6 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 530-539 1195753-1201291 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 540-549 1201604-1205010 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 550-559 1205565-1206985 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 24 590-599 1210748-1212707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 25 600-609 1214335-1218268 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 26 610-619 1218281-1227464 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 27 620-629 1227493-1237444 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 28 630-639 1238228-1240701 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 29 640-649 1242164-1256794 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 30 650-659 1257463-1263928 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 31 660-669 1263967-1274649 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 32 670-679 1274819-1281176 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 33 680-689 1281996-1292727 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 34 690-699 1293196-1298707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 35 700-709 1300366-1312972 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 36 710-719 1313008-1314995 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 37 720-729 1315339-1324219 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 38 730-739 1324575-1334486 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 39 740-749 1334536-1347183 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 40 750-757 1347331-1351516 8 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 391

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 40 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tomorrow night (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't. (Please see below for details what to do in case your hit a report that requires a test script, but for which you cannot create a test script.)

Requirements

Obviously, you need to have MonetDB (plus SQL or XQuery for those bugs) installed and running; preferably an up-to-date ssh-based (non anonymous) CVS check out of either the release branches (MonetDB_4-8, SQL_2-8, XQuery_0-8) or the respective CVS heads. Anonymous (pserver-based) CVS check outs or source distributions should also work, but then you cannot check-in your tests directly (see below on how to participate and submit test script in this case).

Stable vs. Current

In principle, it does not matter, whether you're using the Stable release branch(es) or the Current development head(s). Use what ever you like best (or have already running).

Test directories

Your tests must be located (and hence checked in) in different directories depending on the MonetDB version you're using:

Stable branch: MonetDB 4.8.*: MonetDB/tests/BugDay_2005-11-09_4.8/Tests/ SQL 2.8.*: sql/src/test/BugDay_2005-11-09_2.8/Tests/ XQuery 0.8.*: pathfinder/tests/BugDay_2005-11-09_0.8/Tests/

Current head: MonetDB 4.9.3: MonetDB/tests/BugDay_2005-11-09_4.9.3/Tests/ SQL 2.9.3: sql/src/test/BugDay_2005-11-09_2.9.3/Tests/ XQuery 0.9.3: pathfinder/tests/BugDay_2005-11-09_0.9.3/Tests/

The reason for having different directories is mainly convenience with check-ins and later propagations.

Codes

To indicate the progress (see below for details), please use the following codes when adding comments to the bug report

code explanation ------------------------+--------------------------------------------- RELEASED / REASSIGN | the "claimer" of the bug wasn't able to create a | script from the bug due to insufficient | knowledge. Append reason, e.g. "XQuery". | Also set status of closed bugs to "pending". ALREADY IN TESTWEB | the script was already in CVS and TestWeb | (added location of existing test script). TEST ADDED / SUCCESS | a script was added (append location & name) and | works correctly. TEST ADDED / FAILURE | a script was added, but it fails (bad output). | Re-open closed bug! TEST SUBMITTED | a script was made, but sent to Stefan (for | non-CVS participants) NO TEST / COMPILATION | no test was added because the bug deals with a | compilation problem. NO TEST / DOCUMENTATION | no test was added because the bug deals with a | documentation issue, or misleading help text, | etc. NO TEST / REDUNDANT | no test was added, because either the bug itself | is a duplicate, or the test that follows out of | the bug would clearly be duplicating another | existing bug. When extending another bug to | remove redundancy use TEST ADDED / SUCCESS and | give the name of the already existing updated | bug.

Note: the last action is only meant for experts in their field ;)

An example message on the SF bug could be:

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS sql/src/tests/bugday/like_join_union.SF-0123345.SQL

The Task/Procedure

Claim a chunk of bugs as described above, and then process each bug as follows:

Checking for existence

Once claimed, you first check, whether there is already a test script for this bug (i.e., a test script that contains the respective ID in its filename) available in one of

MonetDB/tests/BugsViaSourgeforce/Tests/ sql/src/test/bugs/Tests/ pathfinder/tests/BugsViaSourgeforce/Tests/

If so, you should indicate this be adding a comment like

BugDay_2005-11-09, <your name>: ALREADY IN TESTWEB MonetDB/tests/BugsViaSourgeforce/Tests/ID.602271.*

to the respective bug report on SF, and you're done with this bug, and can proceed to the next one.

If there is no test script, yet, you need to create one:

Naming conventions

Names of test scripts must include a descriptive part (of reasonable length) and the SF bug ID, like

"return_types_of_head_and_tail.SF-701641.*",

i.e., the pattern is

<descriptive-name>.SF-<BugID>[.<extension>]

Creating test scripts

Most bug reports come with some MIL-, SQL-, XQuery-code, or some other description/instructions how to reproduce the bug. The basic task is to put this into a proper "Mtest-compliant" test script. In most cases, this is just a .milS, .sql, or .xq file. See http://monetdb.cwi.nl/monet/src/testing/README for details about Mtest.py . In case of doubt, please feel free to contact any of your colleagues that might be more familiar with Mtest --- or me of course ;-) Of course, you're welcome to extend the test if appropriate.

In case it is obvious that the bug does not require a test script (e.g., compilation, installation, documentation, or web site bugs), please indicate this by adding a comment like

BugDay_2005-11-09, <your name>: NO TEST / <good reason>

to the respective bug report on SF, and proceed with the next bug.

If a test script is required, but you don't know how to make it (for this particular bug), please feel free to ask for help (or "release" the bug report, again).

Running Mtest

Once you made the test script, you need to run the test. In case you're using `source conf/conf.bash` to setup your MonetDB environment, you can simply call one of

Mtest_MonetDB <descriptive-name>.SF-<BugID> Mtest_sql <descriptive-name>.SF-<BugID> Mtest_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. See `Mtest.py --help` for command line options.

Note: Do NOT change or check-in the "All" file!

This is not required to run tests that are explicitly given on Mtest's command line. I'll will fill the "All" files at the end of the BugDay.

Creating / fixing stable output

After running Mtest, you need to check the output by pointing your browser to the file given at the end of Mtest's console output.

In case the output is correct and as expected, you can approve it by running

Mapprove_MonetDB <descriptive-name>.SF-<BugID> Mapprove_sql <descriptive-name>.SF-<BugID> Mapprove_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above.

In case running the test failed, please fix the test and start again with running Mtest.

In case the output is not correct or no as expected, you first approve the output as described above, but then edit the files

<descriptive-name>.SF-<BugID>.stable.out <descriptive-name>.SF-<BugID>.stable.err

by hand to create the correct/expected output.

In any case, you then re-run Mtest, and check the output by pointing your browser to the file given at the end of Mtest's console output.

In case everything is "green" (i.e., OK), you can check-in all files related to the test (including the stable output!), indicate the success by adding a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / SUCCESS tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and proceed with the next bug.

In case there is still a red 'X' (because MonetDB does not produce the correct/expected output), you also check-in all files, but indicate the problem by a comment like

BugDay_2005-11-09, <your name>: TEST ADDED / FAILURE tests/BugDay_2005-11-09_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

<possibly a description of the failure>

to the respective bug report on SF, and *re-open* this bug report, before proceeding with the next bug.

Anonymous CVS check outs and source distributions

All the above holds, except from the CVS check-in of the new test scripts. Instead, you send me (Stefan.Manegold@cwi.nl) a .tar[.gz] or .zip file including all your new test scripts by the end of your BugDay.

In case you intend to participate without CVS access, please let me know so as soon as you start.

Pooh, I guess that's it for now. I hope, I didn't forget anything --- if so, feel free to ask! (via email, skype, or personally tomorrow at CWI).

cu tomorrow,

Stefan

On Fri, Nov 04, 2005 at 03:34:19PM +0100, Stefan Manegold wrote:

...
(some of you might already have see this one coming; cf. http://www.cwi.nl/htbin/cwwwi/agenda?datum=2005_11+dag=09 ;-))

Dear all,

given the success of the 1st MonetDB-Bug-Day on Oct 06 2005,

8 participants managed to check 347 of the then 721 bug reports, added 97 new test scripts, re-opened some bugs that still/again fail and filed 9 new bug reports; see https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... for details,

there will by a 2nd MonetDB-Bug-Day to (hopefully) check the remaining 347 bug reports (plus those filed since Oct 06 2005), and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Wednesday, Nov 9, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 8:00 - 23:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge, and is reasonably familiar with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README).

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.
   More detailed instructions can be found at 
https://sourceforge.net/mailarchive/forum.php?thread_id=8403629&forum_id... and/or will follow before next Wednesday.

Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the 1st MonetDB-Bug-Day ;-)

Once again thank you very much for your cooperation!

CU next Wednesday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

I claim

...

...
16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Sjoerd Mullender

12:43 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Mine.

-- Sjoerd Mullender

Ying (Jennie) Zhang

12:53 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

Sjoerd,

I believe Martin has just claimed nr 16.

Sjoerd Mullender wrote:

...

...
16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Mine.

Sjoerd Mullender

12:58 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

Stefan Manegold wrote:

...

16 440-449 1114000-1119186 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 524-529 1190980-1194362 6 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

I relinquish 16 to Martin and claim 17 instead.

-- Sjoerd Mullender

Niels Nes

1:26 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

18 530-539 1195753-1201291 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

mine

Niels

Stefan Manegold

1:28 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

I'll proceed with 19

...

19 540-549 1201604-1205010 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 550-559 1205565-1206985 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

since Peter had already claimed 20, the next one is to proceed with 21 onward...

Stefan

...

21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 24 590-599 1210748-1212707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 25 600-609 1214335-1218268 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 26 610-619 1218281-1227464 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 27 620-629 1227493-1237444 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 28 630-639 1238228-1240701 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 29 640-649 1242164-1256794 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 30 650-659 1257463-1263928 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 31 660-669 1263967-1274649 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 32 670-679 1274819-1281176 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 33 680-689 1281996-1292727 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 34 690-699 1293196-1298707 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 35 700-709 1300366-1312972 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 36 710-719 1313008-1314995 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 37 720-729 1315339-1324219 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 38 730-739 1324575-1334486 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 39 740-749 1334536-1347183 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 40 750-757 1347331-1351516 8 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Ying (Jennie) Zhang

1:48 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

since Peter had already claimed 20, the next one is to proceed with 21 onward...

...

...
21 560-569 1207029-1207516 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Then I will go on with nr 21

Jennie

Sjoerd Mullender

2:04 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

Stefan Manegold wrote:

...

22 570-579 1207625-1208129 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Mine.

-- Sjoerd Mullender

Niels Nes

2:37 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Wed, Nov 9 2005 (tomorrow)

...

23 580-589 1208599-1210743 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Mine

Niels

Stefan Manegold

8:41 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Results

Dear all,

here's a short summary of the results of the 2nd MonetDB-Bug-Day:

(active) participants: 7 Bug reports checked: 213 test scripts added: 60 open bugs fixed: ? closed bgus re-open: some sweets: ~700g soft-drinks: 1 beers: 2^H3

Thank you all VERY MUCH for your help!

Good night,

Stefan

ps: some detail for the bookkeeping and for the 3rd MonetDB-Bug-Day (yes, I'll keep on teasing you ... ;-))

Unfortunately, we currently have 65 (!) open bug reports ... |-((

Done (i.e., checked and test scripts added): ============================================ No Offsets BugIDs # who -------------------------------------- 1 213-219 947600- 949071 7 Jenny 2 220-229 949135- 952758 10 Jenny 3 230-239 953545- 963620 10 Niels 4 240-249 963759- 971158 10 Niels 5 330-339 1023645-1025005 10 Stefan 6 340-349 1025062-1029058 10 Sjoerd 7 350-359 1029099-1034613 10 Niels 8 360-369 1034922-1037591 10 Stefan 9 370-379 1037993-1043526 10 Niels 10 380-389 1044534-1063089 10 Fabian 11 390-399 1065373-1076344 10 Wouter 12 400-409 1076604-1081218 10 Jenny 13 410-419 1081274-1085120 10 Sjoerd 14 420-429 1085355-1099345 10 Stefan 15 430-439 1100291-1113994 10 Niels 16 440-449 1114000-1119186 10 Martin 17 524-529 1190980-1194362 6 Sjoerd 18 530-539 1195753-1201291 10 Niels 19 540-549 1201604-1205010 10 Stefan 21 560-569 1207029-1207516 10 Jenny 22 570-579 1207625-1208129 10 Sjoerd 23 580-589 1208599-1210743 10 Niels --- 213

Ying (Jennie) Zhang

9:05 p.m.

New subject: [Monetdb-developers] Re: 2nd MonetDB-Bug-Day: Results

Stefan Manegold wrote:

...

Dear all,

here's a short summary of the results of the 2nd MonetDB-Bug-Day:

(active) participants: 7 Bug reports checked: 213

It's not yet middlenight and Niels is still working, so this number might be increased by tomorrow:)

Stefan Manegold

16 Dec 16 Dec

12:52 p.m.

New subject: [Monetdb-developers] 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (next Monday)

Dear all,

given the success of the first two MonetDB-Bug-Days on Oct 06 2005 and Nov 09 2005,

--- we managed to check 460 bug reports, added missing test scripts, re-opened bugs that still/again fail and filed new bug reports ---

there will by a 3rd MonetDB-Bug-Day to (hopefully) check the remaining ~225 bug reports, and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: MOnday, Dec 19, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 9:00 - 17:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge; experiences with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README) are helpful, but can also be aquired during the MonetDB-Bug-Day.

More detailed instructions will follow before Monday.

I hope to see especially (though not only) participants that I haven't seen on the previous MonetDB-Bug-Days ;-)

Once again thank you very much for your cooperation!

CU next Monday,

Stefan

Stefan Manegold

19 Dec 19 Dec

12:33 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

Dear all,

here are some more informations for the 3rd MonetDB-Bug-Day today.

Please note, though it's called Bug-*Day*, you don't have to spend the whole day writing test scripts (though no one would mind if you do ;-)). Below you find chunks of 10 bug reports each; simply claim one chunk at a time (by group-reply to this email) whenever you feel like you could spend some minutes on this "community task", check the 10 reports and provide the test script where necessary/applicable. If we don't manage to finish the 21 chunks tomorrow, everybody is welcome to pick more chunk(s) any time later...

Of course, next to (or instead of) adding test scripts, you're also welcome to fix open bugs (and add the test script for each bug you fix)!

Chunks ======

No Offsets BugIDs # URL -------------------------------------- 1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

General issues ==============

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 21 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tonight (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't. (Please see below for details what to do in case your hit a report that requires a test script, but for which you cannot create a test script.)

Requirements ============

Stable vs. Current ------------------

In principle, it does not matter, whether you're using the Stable release branch(es) or the Current development head(s). Use what ever you like best (or have already running).

Test directories ----------------

Your tests must be located (and hence checked in) in the following directories:

MonetDB 4.9.3: MonetDB/tests/BugDay_2005-12-19_4.9.3/Tests/ SQL 2.9.3: sql/src/test/BugDay_2005-12-19_2.9.3/Tests/ XQuery 0.9.3: pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/

Codes =====

To indicate the progress (see below for details), please use the following codes when adding comments to the bug report

Note: the last action is only meant for experts in their field ;)

An example message on the SF bug could be:

BugDay_2005-12-19, <your name>: TEST ADDED / SUCCESS sql/src/tests/bugday/like_join_union.SF-0123345.SQL

The Task/Procedure ==================

Claim a chunk of bugs as described above, and then process each bug as follows:

Checking for existence ----------------------

Once claimed, you first check, whether there is already a test script for this bug (i.e., a test script that contains the respective ID in its filename) available in one of

MonetDB/tests/BugsViaSourgeforce/Tests/ sql/src/test/bugs/Tests/ pathfinder/tests/BugsViaSourgeforce/Tests/

If so, you should indicate this be adding a comment like

BugDay_2005-12-19, <your name>: ALREADY IN TESTWEB MonetDB/tests/BugsViaSourgeforce/Tests/ID.602271.*

to the respective bug report on SF, and you're done with this bug, and can proceed to the next one.

If there is no test script, yet, you need to create one:

Naming conventions ------------------

Names of test scripts must include a descriptive part (of reasonable length) and the SF bug ID, like

"return_types_of_head_and_tail.SF-701641.*",

i.e., the pattern is

<descriptive-name>.SF-<BugID>[.<extension>]

Creating test scripts ---------------------

In case it is obvious that the bug does not require a test script (e.g., compilation, installation, documentation, or web site bugs), please indicate this by adding a comment like

BugDay_2005-12-19, <your name>: NO TEST / <good reason>

to the respective bug report on SF, and proceed with the next bug.

If a test script is required, but you don't know how to make it (for this particular bug), please feel free to ask for help (or "release" the bug report, again).

Running Mtest -------------

Once you made the test script, you need to run the test. In case you're using `source conf/conf.bash` to setup your MonetDB environment, you can simply call one of

Mtest_MonetDB <descriptive-name>.SF-<BugID> Mtest_sql <descriptive-name>.SF-<BugID> Mtest_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. See `Mtest.py --help` for command line options.

Note: Do NOT change or check-in the "All" file!

This is not required to run tests that are explicitly given on Mtest's command line. I'll will fill the "All" files at the end of the BugDay.

Creating / fixing stable output -------------------------------

After running Mtest, you need to check the output by pointing your browser to the file given at the end of Mtest's console output.

In case the output is correct and as expected, you can approve it by running

Mapprove_MonetDB <descriptive-name>.SF-<BugID> Mapprove_sql <descriptive-name>.SF-<BugID> Mapprove_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. In case running the test failed, please fix the test and start again with running Mtest.

In case the output is not correct or not as expected, you first approve the output as described above, but then edit the files

<descriptive-name>.SF-<BugID>.stable.out <descriptive-name>.SF-<BugID>.stable.err

by hand to create the correct/expected output.

In any case, you then re-run Mtest, and check the output by pointing your browser to the file given at the end of Mtest's console output.

In case everything is "green" (i.e., OK), you can check-in all files related to the test (including the stable output!), indicate the success by adding a comment like

BugDay_2005-12-19, <your name>: TEST ADDED / SUCCESS tests/BugDay_2005-12-19_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and proceed with the next bug.

In case there is still a red 'X' (because MonetDB does not produce the correct/expected output), you also check-in all files, but indicate the problem by a comment like

BugDay_2005-12-19, <your name>: TEST ADDED / FAILURE tests/BugDay_2005-12-19_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and *re-open* this bug report, before proceeding with the next bug.

Anonymous CVS check outs and source distributions =================================================

In case you intend to participate without CVS access, please let me know so as soon as you start.

Pooh, I guess that's it for now. I hope, I didn't forget anything --- if so, feel free to ask! (via email, skype, or personally later at CWI).

cu later,

Stefan

On Fri, Dec 16, 2005 at 01:52:30PM +0100, Stefan Manegold wrote:

...

Dear all,

given the success of the first two MonetDB-Bug-Days on Oct 06 2005 and Nov 09 2005,

--- we managed to check 460 bug reports, added missing test scripts, re-opened bugs that still/again fail and filed new bug reports ---

there will by a 3rd MonetDB-Bug-Day to (hopefully) check the remaining ~225 bug reports, and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Monday, Dec 19, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 9:00 - 17:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge; experiences with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README) are helpful, but can also be aquired during the MonetDB-Bug-Day.

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.
    More detailed instructions will follow before Monday.
Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the previous MonetDB-Bug-Days ;-)

Once again thank you very much for your cooperation!

CU next Monday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!

Niels Nes

7:41 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Mon, Dec 19, 2005 at 01:33:38AM +0100, Stefan Manegold wrote:

...

Dear all,

here are some more informations for the 3rd MonetDB-Bug-Day today.

Please note, though it's called Bug-*Day*, you don't have to spend the whole day writing test scripts (though no one would mind if you do ;-)). Below you find chunks of 10 bug reports each; simply claim one chunk at a time (by group-reply to this email) whenever you feel like you could spend some minutes on this "community task", check the 10 reports and provide the test script where necessary/applicable. If we don't manage to finish the 21 chunks tomorrow, everybody is welcome to pick more chunk(s) any time later...

Of course, next to (or instead of) adding test scripts, you're also welcome to fix open bugs (and add the test script for each bug you fix)!

Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Claim..

Niels

...

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

General issues

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 21 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tonight (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't. (Please see below for details what to do in case your hit a report that requires a test script, but for which you cannot create a test script.)

Requirements

Obviously, you need to have MonetDB (plus SQL or XQuery for those bugs) installed and running; preferably an up-to-date ssh-based (non anonymous) CVS check out of either the release branches (MonetDB_4-8, SQL_2-8, XQuery_0-8) or the respective CVS heads. Anonymous (pserver-based) CVS check outs or source distributions should also work, but then you cannot check-in your tests directly (see below on how to participate and submit test script in this case).

Stable vs. Current

In principle, it does not matter, whether you're using the Stable release branch(es) or the Current development head(s). Use what ever you like best (or have already running).

Test directories

Your tests must be located (and hence checked in) in the following directories:

MonetDB 4.9.3: MonetDB/tests/BugDay_2005-12-19_4.9.3/Tests/ SQL 2.9.3: sql/src/test/BugDay_2005-12-19_2.9.3/Tests/ XQuery 0.9.3: pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/

Codes

To indicate the progress (see below for details), please use the following codes when adding comments to the bug report

code explanation ------------------------+--------------------------------------------- RELEASED / REASSIGN | the "claimer" of the bug wasn't able to create a | script from the bug due to insufficient | knowledge. Append reason, e.g. "XQuery". | Also set status of closed bugs to "pending". ALREADY IN TESTWEB | the script was already in CVS and TestWeb | (added location of existing test script). TEST ADDED / SUCCESS | a script was added (append location & name) and | works correctly. TEST ADDED / FAILURE | a script was added, but it fails (bad output). | Re-open closed bug! TEST SUBMITTED | a script was made, but sent to Stefan (for | non-CVS participants) NO TEST / COMPILATION | no test was added because the bug deals with a | compilation problem. NO TEST / DOCUMENTATION | no test was added because the bug deals with a | documentation issue, or misleading help text, | etc. NO TEST / REDUNDANT | no test was added, because either the bug itself | is a duplicate, or the test that follows out of | the bug would clearly be duplicating another | existing bug. When extending another bug to | remove redundancy use TEST ADDED / SUCCESS and | give the name of the already existing updated | bug.

Note: the last action is only meant for experts in their field ;)

An example message on the SF bug could be:

BugDay_2005-12-19, <your name>: TEST ADDED / SUCCESS sql/src/tests/bugday/like_join_union.SF-0123345.SQL

The Task/Procedure

Claim a chunk of bugs as described above, and then process each bug as follows:

Checking for existence

Once claimed, you first check, whether there is already a test script for this bug (i.e., a test script that contains the respective ID in its filename) available in one of

MonetDB/tests/BugsViaSourgeforce/Tests/ sql/src/test/bugs/Tests/ pathfinder/tests/BugsViaSourgeforce/Tests/

If so, you should indicate this be adding a comment like

BugDay_2005-12-19, <your name>: ALREADY IN TESTWEB MonetDB/tests/BugsViaSourgeforce/Tests/ID.602271.*

to the respective bug report on SF, and you're done with this bug, and can proceed to the next one.

If there is no test script, yet, you need to create one:

Naming conventions

Names of test scripts must include a descriptive part (of reasonable length) and the SF bug ID, like

"return_types_of_head_and_tail.SF-701641.*",

i.e., the pattern is

<descriptive-name>.SF-<BugID>[.<extension>]

Creating test scripts

Most bug reports come with some MIL-, SQL-, XQuery-code, or some other description/instructions how to reproduce the bug. The basic task is to put this into a proper "Mtest-compliant" test script. In most cases, this is just a .milS, .sql, or .xq file. See http://monetdb.cwi.nl/monet/src/testing/README for details about Mtest.py . In case of doubt, please feel free to contact any of your colleagues that might be more familiar with Mtest --- or me of course ;-) Of course, you're welcome to extend the test if appropriate.

In case it is obvious that the bug does not require a test script (e.g., compilation, installation, documentation, or web site bugs), please indicate this by adding a comment like

BugDay_2005-12-19, <your name>: NO TEST / <good reason>

to the respective bug report on SF, and proceed with the next bug.

If a test script is required, but you don't know how to make it (for this particular bug), please feel free to ask for help (or "release" the bug report, again).

Running Mtest

Once you made the test script, you need to run the test. In case you're using `source conf/conf.bash` to setup your MonetDB environment, you can simply call one of

Mtest_MonetDB <descriptive-name>.SF-<BugID> Mtest_sql <descriptive-name>.SF-<BugID> Mtest_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. See `Mtest.py --help` for command line options.

Note: Do NOT change or check-in the "All" file!

This is not required to run tests that are explicitly given on Mtest's command line. I'll will fill the "All" files at the end of the BugDay.

Creating / fixing stable output

After running Mtest, you need to check the output by pointing your browser to the file given at the end of Mtest's console output.

In case the output is correct and as expected, you can approve it by running

Mapprove_MonetDB <descriptive-name>.SF-<BugID> Mapprove_sql <descriptive-name>.SF-<BugID> Mapprove_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above.

In case running the test failed, please fix the test and start again with running Mtest.

In case the output is not correct or not as expected, you first approve the output as described above, but then edit the files

<descriptive-name>.SF-<BugID>.stable.out <descriptive-name>.SF-<BugID>.stable.err

by hand to create the correct/expected output.

In any case, you then re-run Mtest, and check the output by pointing your browser to the file given at the end of Mtest's console output.

In case everything is "green" (i.e., OK), you can check-in all files related to the test (including the stable output!), indicate the success by adding a comment like

BugDay_2005-12-19, <your name>: TEST ADDED / SUCCESS tests/BugDay_2005-12-19_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and proceed with the next bug.

In case there is still a red 'X' (because MonetDB does not produce the correct/expected output), you also check-in all files, but indicate the problem by a comment like

BugDay_2005-12-19, <your name>: TEST ADDED / FAILURE tests/BugDay_2005-12-19_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

<possibly a description of the failure>

to the respective bug report on SF, and *re-open* this bug report, before proceeding with the next bug.

Anonymous CVS check outs and source distributions

All the above holds, except from the CVS check-in of the new test scripts. Instead, you send me (Stefan.Manegold@cwi.nl) a .tar[.gz] or .zip file including all your new test scripts by the end of your BugDay.

In case you intend to participate without CVS access, please let me know so as soon as you start.

Pooh, I guess that's it for now. I hope, I didn't forget anything --- if so, feel free to ask! (via email, skype, or personally later at CWI).

cu later,

Stefan

On Fri, Dec 16, 2005 at 01:52:30PM +0100, Stefan Manegold wrote:

...
Dear all,

given the success of the first two MonetDB-Bug-Days on Oct 06 2005 and Nov 09 2005,

--- we managed to check 460 bug reports, added missing test scripts, re-opened bugs that still/again fail and filed new bug reports ---

there will by a 3rd MonetDB-Bug-Day to (hopefully) check the remaining ~225 bug reports, and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Monday, Dec 19, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 9:00 - 17:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge; experiences with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README) are helpful, but can also be aquired during the MonetDB-Bug-Day.

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.
    More detailed instructions will follow before Monday.
Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the previous MonetDB-Bug-Days ;-)

Once again thank you very much for your cooperation!

CU next Monday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

Niels Nes

8:34 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Mon, Dec 19, 2005 at 01:33:38AM +0100, Stefan Manegold wrote:

...

Dear all,

here are some more informations for the 3rd MonetDB-Bug-Day today.

Please note, though it's called Bug-*Day*, you don't have to spend the whole day writing test scripts (though no one would mind if you do ;-)). Below you find chunks of 10 bug reports each; simply claim one chunk at a time (by group-reply to this email) whenever you feel like you could spend some minutes on this "community task", check the 10 reports and provide the test script where necessary/applicable. If we don't manage to finish the 21 chunks tomorrow, everybody is welcome to pick more chunk(s) any time later...

Of course, next to (or instead of) adding test scripts, you're also welcome to fix open bugs (and add the test script for each bug you fix)!

Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Did first 4. ... Have to do something else no ;-)

Niels

...

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

General issues

Please pick one chunk at a time and indicate you choice by (group) replying to this mail. I will resolve clashes where necessary. I don't expect more than 21 people participating (concurrently), hence sub-dividing the chunks should not be necessary ;-) In case you cannot finish your last chunk by tonight (for whatever reason), please let me know (via email) which of the reports you finished, and which you didn't. (Please see below for details what to do in case your hit a report that requires a test script, but for which you cannot create a test script.)

Requirements

Obviously, you need to have MonetDB (plus SQL or XQuery for those bugs) installed and running; preferably an up-to-date ssh-based (non anonymous) CVS check out of either the release branches (MonetDB_4-8, SQL_2-8, XQuery_0-8) or the respective CVS heads. Anonymous (pserver-based) CVS check outs or source distributions should also work, but then you cannot check-in your tests directly (see below on how to participate and submit test script in this case).

Stable vs. Current

In principle, it does not matter, whether you're using the Stable release branch(es) or the Current development head(s). Use what ever you like best (or have already running).

Test directories

Your tests must be located (and hence checked in) in the following directories:

MonetDB 4.9.3: MonetDB/tests/BugDay_2005-12-19_4.9.3/Tests/ SQL 2.9.3: sql/src/test/BugDay_2005-12-19_2.9.3/Tests/ XQuery 0.9.3: pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/

Codes

To indicate the progress (see below for details), please use the following codes when adding comments to the bug report

code explanation ------------------------+--------------------------------------------- RELEASED / REASSIGN | the "claimer" of the bug wasn't able to create a | script from the bug due to insufficient | knowledge. Append reason, e.g. "XQuery". | Also set status of closed bugs to "pending". ALREADY IN TESTWEB | the script was already in CVS and TestWeb | (added location of existing test script). TEST ADDED / SUCCESS | a script was added (append location & name) and | works correctly. TEST ADDED / FAILURE | a script was added, but it fails (bad output). | Re-open closed bug! TEST SUBMITTED | a script was made, but sent to Stefan (for | non-CVS participants) NO TEST / COMPILATION | no test was added because the bug deals with a | compilation problem. NO TEST / DOCUMENTATION | no test was added because the bug deals with a | documentation issue, or misleading help text, | etc. NO TEST / REDUNDANT | no test was added, because either the bug itself | is a duplicate, or the test that follows out of | the bug would clearly be duplicating another | existing bug. When extending another bug to | remove redundancy use TEST ADDED / SUCCESS and | give the name of the already existing updated | bug.

Note: the last action is only meant for experts in their field ;)

An example message on the SF bug could be:

BugDay_2005-12-19, <your name>: TEST ADDED / SUCCESS sql/src/tests/bugday/like_join_union.SF-0123345.SQL

The Task/Procedure

Claim a chunk of bugs as described above, and then process each bug as follows:

Checking for existence

Once claimed, you first check, whether there is already a test script for this bug (i.e., a test script that contains the respective ID in its filename) available in one of

MonetDB/tests/BugsViaSourgeforce/Tests/ sql/src/test/bugs/Tests/ pathfinder/tests/BugsViaSourgeforce/Tests/

If so, you should indicate this be adding a comment like

BugDay_2005-12-19, <your name>: ALREADY IN TESTWEB MonetDB/tests/BugsViaSourgeforce/Tests/ID.602271.*

to the respective bug report on SF, and you're done with this bug, and can proceed to the next one.

If there is no test script, yet, you need to create one:

Naming conventions

Names of test scripts must include a descriptive part (of reasonable length) and the SF bug ID, like

"return_types_of_head_and_tail.SF-701641.*",

i.e., the pattern is

<descriptive-name>.SF-<BugID>[.<extension>]

Creating test scripts

Most bug reports come with some MIL-, SQL-, XQuery-code, or some other description/instructions how to reproduce the bug. The basic task is to put this into a proper "Mtest-compliant" test script. In most cases, this is just a .milS, .sql, or .xq file. See http://monetdb.cwi.nl/monet/src/testing/README for details about Mtest.py . In case of doubt, please feel free to contact any of your colleagues that might be more familiar with Mtest --- or me of course ;-) Of course, you're welcome to extend the test if appropriate.

In case it is obvious that the bug does not require a test script (e.g., compilation, installation, documentation, or web site bugs), please indicate this by adding a comment like

BugDay_2005-12-19, <your name>: NO TEST / <good reason>

to the respective bug report on SF, and proceed with the next bug.

If a test script is required, but you don't know how to make it (for this particular bug), please feel free to ask for help (or "release" the bug report, again).

Running Mtest

Once you made the test script, you need to run the test. In case you're using `source conf/conf.bash` to setup your MonetDB environment, you can simply call one of

Mtest_MonetDB <descriptive-name>.SF-<BugID> Mtest_sql <descriptive-name>.SF-<BugID> Mtest_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above. See `Mtest.py --help` for command line options.

Note: Do NOT change or check-in the "All" file!

This is not required to run tests that are explicitly given on Mtest's command line. I'll will fill the "All" files at the end of the BugDay.

Creating / fixing stable output

After running Mtest, you need to check the output by pointing your browser to the file given at the end of Mtest's console output.

In case the output is correct and as expected, you can approve it by running

Mapprove_MonetDB <descriptive-name>.SF-<BugID> Mapprove_sql <descriptive-name>.SF-<BugID> Mapprove_pathfinder <descriptive-name>.SF-<BugID>

in the respective directory as listed above.

In case running the test failed, please fix the test and start again with running Mtest.

In case the output is not correct or not as expected, you first approve the output as described above, but then edit the files

<descriptive-name>.SF-<BugID>.stable.out <descriptive-name>.SF-<BugID>.stable.err

by hand to create the correct/expected output.

In any case, you then re-run Mtest, and check the output by pointing your browser to the file given at the end of Mtest's console output.

In case everything is "green" (i.e., OK), you can check-in all files related to the test (including the stable output!), indicate the success by adding a comment like

BugDay_2005-12-19, <your name>: TEST ADDED / SUCCESS tests/BugDay_2005-12-19_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

to the respective bug report on SF, and proceed with the next bug.

In case there is still a red 'X' (because MonetDB does not produce the correct/expected output), you also check-in all files, but indicate the problem by a comment like

BugDay_2005-12-19, <your name>: TEST ADDED / FAILURE tests/BugDay_2005-12-19_4.9.3/Tests/return_types_of_head_and_tail.SF-701641.*

<possibly a description of the failure>

to the respective bug report on SF, and *re-open* this bug report, before proceeding with the next bug.

Anonymous CVS check outs and source distributions

All the above holds, except from the CVS check-in of the new test scripts. Instead, you send me (Stefan.Manegold@cwi.nl) a .tar[.gz] or .zip file including all your new test scripts by the end of your BugDay.

In case you intend to participate without CVS access, please let me know so as soon as you start.

Pooh, I guess that's it for now. I hope, I didn't forget anything --- if so, feel free to ask! (via email, skype, or personally later at CWI).

cu later,

Stefan

On Fri, Dec 16, 2005 at 01:52:30PM +0100, Stefan Manegold wrote:

...
Dear all,

given the success of the first two MonetDB-Bug-Days on Oct 06 2005 and Nov 09 2005,

--- we managed to check 460 bug reports, added missing test scripts, re-opened bugs that still/again fail and filed new bug reports ---

there will by a 3rd MonetDB-Bug-Day to (hopefully) check the remaining ~225 bug reports, and produce proper test scripts for our automatic Nightly Multi-Platform Regression Test System (aka "TestWeb"; cf. http://monetdb.cwi.nl/Development/TestWeb/):

When: Monday, Dec 19, 2005, "all day" (or as much time as you can spent)

Where: Mainly at CWI, but you're also welcome to join "virtually" working from home or any other place in the world; for those who (again) want to turn the Bug-Day into a Bug-"Party", I reserved our meeting room (C0,01) from 9:00 - 17:00 --- you need to bring your own "equipment" though ...

Who: Primarily everyone who is in touch with MonetDB, and/or one of its companions/front ends (SQL, XQuery, etc.), has rights to check-in to the MonetDB CVS repository on SourceForge; experiences with "Mtest.py" (cf. http://monetdb.cwi.nl/monet/src/testing/README) are helpful, but can also be aquired during the MonetDB-Bug-Day.

What: I will prepare a list of all bugs that have no test script, yet, and chop this in chunks, and assign each chunk to one participant so that [s]he can check them, and prepare the respective test scripts.
    More detailed instructions will follow before Monday.
Note: Though any help is appreciated, no one is "obliged" to help. Especially, there is no need to spent the whole day (though nine will complain if you do ;-)), anyone can join-in and leave whenever [s]he wants.

For those of you participating at CWI, there will be free snacks and soft-drinks during the day (for the time you're "active"; as long as supplies lasts). Furthermore, there will be "real" drinks at the end of the Bug-Day (for participants, only; as long as supplies lasts; (maximum) amount per person will be proportional to the number of test scripts added).

I hope to see especially (though not only) participants that I haven't seen on the previous MonetDB-Bug-Days ;-)

Once again thank you very much for your cooperation!

CU next Monday,

Stefan

ps: Testing & the TestWeb are not (only?) my "toys"; it's "serious business", and helps all of you to (1) get a stable and reliable MonetDB, (2) monitor when your own bug reports get fixed, and (3) prevent the bugs you once thankfully detected, reported and/or fixed from occurring again!
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

Fabian Groffen

8:38 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On 19-12-2005 09:34:52 +0100, Niels Nes wrote:

...

...
Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Did first 4. ... Have to do something else no ;-)

Niels

...
3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

I take these

...

...
4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Fabian Groffen

9:11 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On 19-12-2005 09:38:16 +0100, Fabian Groffen wrote:

...

On 19-12-2005 09:34:52 +0100, Niels Nes wrote:

...
...
Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Did first 4. ... Have to do something else no ;-)

Niels

...
3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...

...
...
4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

mine

...

...
...
5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Stefan Manegold

9:47 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Mon, Dec 19, 2005 at 10:11:18AM +0100, Fabian Groffen wrote:

...

On 19-12-2005 09:38:16 +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:34:52 +0100, Niels Nes wrote:

...
...
Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Did first 4. ... Have to do something else no ;-)

continuing where Niels stopped.

Stefan

...

...
...
Niels

...
3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
...
...
4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

mine

...
...
...
5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Ying Zhang

9:52 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Mon, Dec 19, 2005 at 10:47:21AM +0100, Stefan Manegold wrote:

...

On Mon, Dec 19, 2005 at 10:11:18AM +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:38:16 +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:34:52 +0100, Niels Nes wrote:

...
...
Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Did first 4. ... Have to do something else no ;-)

continuing where Niels stopped.

Stefan

...
...
...
Niels

...
3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
...
...
4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

mine

...
...
...
5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

take this one

...

...
...
...
...
6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

Sjoerd Mullender

10:35 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

Ying Zhang wrote:

...

On Mon, Dec 19, 2005 at 10:47:21AM +0100, Stefan Manegold wrote:

...
On Mon, Dec 19, 2005 at 10:11:18AM +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:38:16 +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:34:52 +0100, Niels Nes wrote:

...
...
Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Did first 4. ... Have to do something else no ;-)

continuing where Niels stopped.

Stefan

...
...
...
Niels

...
3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
...
...
4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

mine

...
...
...
5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

take this one

...
...
...
...
...
6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

6 is mine.

...

...
...
...
...
...
7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers

-- Sjoerd Mullender

Sjoerd Mullender

12:31 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

Sjoerd Mullender wrote:

...

Ying Zhang wrote:

...
On Mon, Dec 19, 2005 at 10:47:21AM +0100, Stefan Manegold wrote:

...
On Mon, Dec 19, 2005 at 10:11:18AM +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:38:16 +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:34:52 +0100, Niels Nes wrote:

...
>Chunks >====== > >No Offsets BugIDs # URL >-------------------------------------- >1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

>2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Did first 4. ... Have to do something else no ;-)

continuing where Niels stopped.

Stefan

...
...
...
Niels

>3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
...
>4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

mine

...
...
>5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

take this one

...
...
...
...
>6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

6 is mine.

...
...
...
...
...
>7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

I'll go on with 7.

...

...
...
...
...
...
>8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... > >13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... > --- > 209

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers

-- Sjoerd Mullender

Sjoerd Mullender

2:02 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

Sjoerd Mullender wrote:

...

Sjoerd Mullender wrote:

...
Ying Zhang wrote:

...
On Mon, Dec 19, 2005 at 10:47:21AM +0100, Stefan Manegold wrote:

...
On Mon, Dec 19, 2005 at 10:11:18AM +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:38:16 +0100, Fabian Groffen wrote:

...
On 19-12-2005 09:34:52 +0100, Niels Nes wrote:

>>Chunks >>====== >> >>No Offsets BugIDs # URL >>-------------------------------------- >>1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... > >done > > > >>2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... > >Did first 4. ... Have to do something else no ;-)

continuing where Niels stopped.

Stefan

...
...
>Niels > > > >>3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

done

...
>>4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

mine

...
>>5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

take this one

...
...
...
>>6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

6 is mine.

...
...
...
...
>>7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

I'll go on with 7.

...
...
...
...
...
>>8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

On with 8.

...

...
...
...
...
...
>>9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >> >>13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >>21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... >> --- >> 209

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers

-- Sjoerd Mullender

Stefan Manegold

2:36 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

...

Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...

10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Sjoerd Mullender

2:45 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

Stefan Manegold wrote:

...

...
Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...
10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Sjoerd

...

...
11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

-- Sjoerd Mullender

Stefan Manegold

3:02 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

...

Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...

12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Sjoerd Mullender

3:35 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

Stefan Manegold wrote:

...

...
Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...
12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Sjoerd

...

...
13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

-- Sjoerd Mullender

Stefan Manegold

3:36 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

...

Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Stefan Manegold

3:38 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Mon, Dec 19, 2005 at 04:36:17PM +0100, Stefan Manegold wrote:

...

Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...

14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Stefan Manegold

9:11 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

...

Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...

16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Niels Nes

9:25 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Mon, Dec 19, 2005 at 10:11:24PM +0100, Stefan Manegold wrote:

...

...
Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...
16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Claimed ..

Niels

...

...
17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

Stefan Manegold

10:15 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

...

Chunks

No Offsets BugIDs # URL

1 550-558 1206432-1206985 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

2 589-599 1210748-1214335 11 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels & Stefan

3 600-609 1214372-1218281 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

4 610-619 1218291-1227493 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Fabian

5 620-629 1229018-1238228 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Jennie

6 630-639 1238352-1242164 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

7 640-649 1244326-1257463 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

8 650-659 1259668-1263967 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

9 660-669 1265413-1274819 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

10 670-679 1274903-1281996 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

11 680-689 1283842-1293196 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

12 690-698 1294712-1298707 9 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Sjoerd

13 710-719 1313271-1315339 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

14 720-729 1315653-1324575 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

15 730-739 1327854-1334536 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Stefan

16 740-749 1337630-1347331 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

17 750-759 1347758-1353883 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...

18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 209

Stefan Manegold

11:10 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

For the book keeping: These chunks are left for tomorrow (Tuesday) and/or Wednesday:

No Offsets BugIDs # URL -------------------------------------- 18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 40

Stefan

Niels Nes

20 Dec 20 Dec

6:54 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Tue, Dec 20, 2005 at 12:10:26AM +0100, Stefan Manegold wrote:

...

For the book keeping: These chunks are left for tomorrow (Tuesday) and/or Wednesday:

No Offsets BugIDs # URL

18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

claimed

Niels

...

19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 40

Stefan

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers

Stefan Manegold

10:41 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

...

No Offsets BugIDs # URL

18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...

20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 40

Sjoerd Mullender

12:49 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

Stefan Manegold wrote:

...

...
No Offsets BugIDs # URL

18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... Niels

19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

Stefan

...
20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

I'll take the last one.

-- Sjoerd Mullender

Ying Zhang

10:41 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Tue, Dec 20, 2005 at 07:54:23AM +0100, Niels Nes wrote:

...

On Tue, Dec 20, 2005 at 12:10:26AM +0100, Stefan Manegold wrote:

...
For the book keeping: These chunks are left for tomorrow (Tuesday) and/or Wednesday:

No Offsets BugIDs # URL

18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

claimed

Niels

...
19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

take this

...

...
20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... 21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&... --- 40

Stefan

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers

--

Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl

Ying Zhang

10:43 a.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Mon, Dec 19 2005 (today)

On Tue, Dec 20, 2005 at 11:41:35AM +0100, Ying Zhang wrote:

...

On Tue, Dec 20, 2005 at 07:54:23AM +0100, Niels Nes wrote:

...
On Tue, Dec 20, 2005 at 12:10:26AM +0100, Stefan Manegold wrote:

...
For the book keeping: These chunks are left for tomorrow (Tuesday) and/or Wednesday:

No Offsets BugIDs # URL

18 760-769 1354321-1358222 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

claimed

Niels

...
19 770-779 1359071-1363729 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

take this

...
...
20 780-789 1363733-1371524 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

oeps, sorry, didn't see stefan's e-mail. take this one, then.

...

...
...
21 790-799 1373391-1380287 10 http://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...
                          40
Stefan

-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |

This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
--

Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl

Stefan Manegold

5:03 p.m.

New subject: [Monetdb-developers] Re: 3rd MonetDB-Bug-Day: Results and Future Work

Dear all,

all the remaining 209 bug reports have been check yesterday and today.

Thank you all very much for your help with the three MonetDB-Bug-Days.

Two task still remain:

1) Re-check all bug reports that are set to "pending" and add proper test scripts for them: https://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

2) Take care of all open bugs and fix them: https://sourceforge.net/tracker/index.php?func=browse&group_id=56967&...

For the future, we should implement the new Bug-Etiquette, that no bug report may be closed, unless a test script (incl. correct output!) has been added to the CVS repository (and hence the automatic testing system). The developer/assignee that closes the bug report is responsible for ensuring that a proper test script is available (and that it's location is clearly given in one of the bug reports comments). Of course, users that submit a bug report are more than welcome to also provide a test query/script to reproduce the bug (either simply as a comment or attachment to the bug report, or even as a proper test script in CVS).

Merry Christmas and a Happy New Year!

Stefan

6705

Age (days ago)

6751

Last active (days ago)

List overview

Download

53 comments

8 participants

tags (0)

participants (8)

Fabian Groffen
Martin Kersten
Niels Nes
Sjoerd Mullender
Stefan Manegold
Wouter Alink (CWI)
Ying (Jennie) Zhang
Ying Zhang