Re: [MonetDB-users] MonetSQLdb python API

On Oct 5, 2006, at 11:12 PM, Stefan Manegold wrote:

On Thu, Oct 05, 2006 at 10:31:17AM +0200, Ronald Oussoren wrote:

...

On Tuesday, October 03, 2006, at 01:22PM, Stefan Manegold wrote:

...

...

...

...

'make check' for MonetDB-4.12.1 (downloaded today) complains a lot about:

!ERROR: interpret: no matching MIL operator to 'quit()'. quit();

does this happen with only MonetDB-4.12.1 present on your system, or with a "legacy" MonetDB-4.10.3 installed as well (cf. BTW3 below)?

I've tested again with a clean build of the current snapshot (downloaded half an hour ago), and this gives the same error. Oddly enough running 'make install' and then 'Mtest.py -r' does result in a finished test run. I do get a number of failures:

!ERROR: Testing FAILED SIGNIFICANTLY !

4 out of 313 tests could not be executed 1 out of 313 tests produced slightly different output 6 out of 313 tests produced SIGNIFICANTLY different output

that looks quite normal some tests are known to fail on some architectures;

Hmm, wouldn't it be more useful to add some more logic to the testing infrastructure to deal with this? Your testing infrastructure seems to suffer from the same problem as a lot of other test harnasses: tests don't have two possible outcomes (pass and fail) but four: tests can not only pass or fail, but can also be expected to fail and do that or not. Adding support for testcases that are supposed to fail should be fairly easy and would reduce confusion when someone that isn't part the development team runs the testsuite ;-) Ronald