Re: [MonetDB-users] MonetSQLdb python API

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; just compare your result to those of our nightly testing; for "Stable" (MonetDB 4.12.1) http://monetdb.cwi.nl/Development/TestWeb/Stable/index.html http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB/.mTests103/ind... for "Current" (MonetDB 4.13.1) http://monetdb.cwi.nl/Development/TestWeb/Current/index.html http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/in... If the same tests fail, that's fine (i.e., known to us, and considered "non-crucial at least for the "Stable" release). If different tests fail, please let us know, preferably with the differences/errors produced by those test.

I can send you the test results, I haven't attached them to this message because the zipfile with the results is about 6 MBytes.

As said, I don't expect the differences to be "crucial", but if you want a detailed analysis, please feel free to send me your results directly.

What I'm doing (on a SuSE Enterprise Linux 9 system on x86):

$ tar zxf MonetDB-4.12.1.tar.gz $ mkdir build $ cd build $ ../MonetDB-4.12.1/configure '--with-php=no' '--with-perl=no' '--with-python=/opt/python2.4/bin/python' '--with-python-incdir=/opt/python2.4/include/python2.4' '-with-python-library=/opt/python2.4/lib' '--with-python-libdir=/opt/python2.4/lib/python2.4/site-packages' '--prefix=/opt/monet-4.12.1' '--enable-debug' '--disable-optimize' $ make $ make check # -> this results in the 'quit' error mentioned earlier $ make install $ Mtest.py -r # -> works correctly

looks perfectly fine to me --- except from the make check problem --- I have to admit, though, that I never tried make check with the tar ball (only from CVS source so far) --- I'll later try it with the tar ball (from our "Daily Builds"), too...

I'll rebuild without debug and with optimization once I have my application running (which mostly requires some further tweaking of the SQLObject ORM for Python).

That fine for a "production environment" (i.e., better performacne ;-)) but will not have any impact on the failing "make check"... 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 |