[MonetDB-users] running 'make check'
Hey, Thanks to Niels Nes, my compilation problems were solved. Just for others who may be reading: it was a bogus mel.yy.cc that I generated on an early compile run without bison and flex installed, and this didn't get removed by 'make clean' (something that will be fixed). Anyway, now I ran 'make check', but not very successfully: !ERROR: Testing FAILED SIGNIFICANTLY ! 3 out of 222 tests could not be executed 219 out of 222 tests produced SIGNIFICANTLY different output Basically typically the output I'd see was like this: 14:56:39> tests/suite_06/test_02.milS (<=60,60,60) ... 0.103s (Killed!) test_02.stable.out.FILTERED and test_02.test.out.FILTERED are equal. test_02.stable.err.FILTERED and test_02.test.err.FILTERED differ SIGNIFICANTLY! 14:56:40> tests/suite_08/test_01.milM (<=60,60,60) ... 0.126s (Killed!) test_01.stable.out.FILTERED and test_01.test.out.FILTERED are equal. test_01.stable.err.FILTERED and test_01.test.err.FILTERED differ SIGNIFICANTLY! 14:56:41> tests/suite_08/test_02.milS (<=60,60,60) ... 0.120s (Killed!) test_02.stable.out.FILTERED and test_02.test.out.FILTERED are equal. test_02.stable.err.FILTERED and test_02.test.err.FILTERED differ SIGNIFICANTLY! Looking at the HTML output, one set of unexpected output looks to be option information like this: # builtin opt config = ${prefix}/etc/MonetDB.conf # builtin opt gdk_arch = 32biti686-pc-linux-gnu # builtin opt gdk_version = 4.8.0 # builtin opt monet_pid = 30545 # builtin opt prefix = /home/faassen/tmp/local # builtin opt exec_prefix = ${prefix} # builtin opt gdk_dbname = tst # builtin opt gdk_dbfarm = ${prefix}/var/MonetDB More seriously, I get this: ! /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests:: No such file or directory ! All: No such file or directory ! client.milC: No such file or directory ! client.stable.err: No such file or directory ! client.stable.out: No such file or directory ! client.stable.out.64bit: No such file or directory ! client.stable.out.64bit.monet_nostalgic.: No such file or directory ... etc Strangely enough, the directory mentioned does exist: faassen@moon:~$ cd /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests faassen@moon:~/working/monet/MonetDB-4.8.0/src/tools/Tests$ pwd /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests and those files, at least at a brief glance, do seem to exist too. Again I guess I'm missing something somewhere.. Regards, Martijn
Hi, Martijn Faassen wrote:
Hey,
<snip />
! /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests:: No such
perhaps these double colons have something to do with it. Our mTest expert will know (and probably tell you). Did you try starting MonetDB(/SQL) anyway? The fact that your system is not able to test, usually doesn't prevent it from running normally, which means you can start enjoying* the MonetDB experience. Regards, Fabian *) in het verleden behaalde rendementen bieden geen garanties voor de toekomst
Fabian wrote: [snip]
! /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests:: No such
perhaps these double colons have something to do with it. Our mTest expert will know (and probably tell you).
Making the tests run will make me feel more comfortable. :)
Did you try starting MonetDB(/SQL) anyway? The fact that your system is not able to test, usually doesn't prevent it from running normally, which means you can start enjoying* the MonetDB experience.
I can start 'Mserver', but I'm new to this so I don't know what to do yet. :) Okay, some testing further, I can get the SQL client going and basic SQL seems to work. An Mtest -r with the installed version results in this: [lots of stuff go here] 18:17:40> scripts/gold/tst100 (<=60,420,420) ...Terminated (and there it ends) Is that normal? Regards, Martijn
On Fri, Jun 03, 2005 at 06:32:11PM +0200, Martijn Faassen wrote:
Fabian wrote: [snip]
! /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests:: No such
perhaps these double colons have something to do with it. Our mTest expert will know (and probably tell you).
Making the tests run will make me feel more comfortable. :)
Did you try starting MonetDB(/SQL) anyway? The fact that your system is not able to test, usually doesn't prevent it from running normally, which means you can start enjoying* the MonetDB experience.
I can start 'Mserver', but I'm new to this so I don't know what to do yet. :) Okay, some testing further, I can get the SQL client going and basic SQL seems to work.
An Mtest -r with the installed version results in this:
[lots of stuff go here] 18:17:40> scripts/gold/tst100 (<=60,420,420) ...Terminated (and there it ends)
Is that normal? No "terminated" is not a normal result.
If you simply start the Mserver and type quit(); does this work? Niels
Regards,
Martijn
-- 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 wrote:
On Fri, Jun 03, 2005 at 06:32:11PM +0200, Martijn Faassen wrote: [snip]
An Mtest -r with the installed version results in this:
[lots of stuff go here] 18:17:40> scripts/gold/tst100 (<=60,420,420) ...Terminated (and there it ends)
Is that normal?
No "terminated" is not a normal result.
If you simply start the Mserver and type quit(); does this work?
Yeah, this appears to work. So do the SQL bits. It's just somewhat worrying the tests don't work. :) Regards, Martijn
going back and reading your mail more closely... can you find any *.stable.err and *.stable.out files in your sources? Where did you get your sources from? Tarball or CVS? Martijn Faassen wrote:
Hey,
Thanks to Niels Nes, my compilation problems were solved. Just for others who may be reading: it was a bogus mel.yy.cc that I generated on an early compile run without bison and flex installed, and this didn't get removed by 'make clean' (something that will be fixed).
Anyway, now I ran 'make check', but not very successfully:
!ERROR: Testing FAILED SIGNIFICANTLY !
3 out of 222 tests could not be executed 219 out of 222 tests produced SIGNIFICANTLY different output
Basically typically the output I'd see was like this:
14:56:39> tests/suite_06/test_02.milS (<=60,60,60) ... 0.103s (Killed!) test_02.stable.out.FILTERED and test_02.test.out.FILTERED are equal. test_02.stable.err.FILTERED and test_02.test.err.FILTERED differ SIGNIFICANTLY! 14:56:40> tests/suite_08/test_01.milM (<=60,60,60) ... 0.126s (Killed!) test_01.stable.out.FILTERED and test_01.test.out.FILTERED are equal. test_01.stable.err.FILTERED and test_01.test.err.FILTERED differ SIGNIFICANTLY! 14:56:41> tests/suite_08/test_02.milS (<=60,60,60) ... 0.120s (Killed!) test_02.stable.out.FILTERED and test_02.test.out.FILTERED are equal. test_02.stable.err.FILTERED and test_02.test.err.FILTERED differ SIGNIFICANTLY!
Looking at the HTML output, one set of unexpected output looks to be option information like this:
# builtin opt config = ${prefix}/etc/MonetDB.conf # builtin opt gdk_arch = 32biti686-pc-linux-gnu # builtin opt gdk_version = 4.8.0 # builtin opt monet_pid = 30545 # builtin opt prefix = /home/faassen/tmp/local # builtin opt exec_prefix = ${prefix} # builtin opt gdk_dbname = tst # builtin opt gdk_dbfarm = ${prefix}/var/MonetDB
More seriously, I get this:
! /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests:: No such file or directory ! All: No such file or directory ! client.milC: No such file or directory ! client.stable.err: No such file or directory ! client.stable.out: No such file or directory ! client.stable.out.64bit: No such file or directory ! client.stable.out.64bit.monet_nostalgic.: No such file or directory ... etc
Strangely enough, the directory mentioned does exist:
faassen@moon:~$ cd /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests faassen@moon:~/working/monet/MonetDB-4.8.0/src/tools/Tests$ pwd /home/faassen/working/monet/MonetDB-4.8.0/src/tools/Tests
and those files, at least at a brief glance, do seem to exist too.
Again I guess I'm missing something somewhere..
Regards,
Martijn
------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Fabian wrote:
going back and reading your mail more closely...
can you find any *.stable.err and *.stable.out files in your sources?
Where did you get your sources from? Tarball or CVS?
Tarball, 4.8.0 from sourceforge. I can find lots of .stable.err and stable.out files scattered in lots of places. Also a lot of stable.out.FILTERED and such. Regards, Martijn
Ok. I took that tarball and did a configure, make and make check. For me it resulted in all tests failing. We didn't find out yet why but it seemed we had a dead symlink somewhere which caused the trouble (!). I would like to have the contents of one of the .err files which 'differ SIGNIFICANTLY', i.e. all files for test_02.test, thus test_02.test.* from tests/suite_06. I'm especially interested in the contents of the .err file, and in particular in the last line, as that is where the problem was visible for me. If not too much trouble we would like to have access to the complete mTest output via a web-page, or via an zip-file, which you can send to my personal mail address. Martijn Faassen wrote:
Fabian wrote:
going back and reading your mail more closely...
can you find any *.stable.err and *.stable.out files in your sources?
Where did you get your sources from? Tarball or CVS?
Tarball, 4.8.0 from sourceforge.
I can find lots of .stable.err and stable.out files scattered in lots of places. Also a lot of stable.out.FILTERED and such.
Regards,
Martijn
Dear Martijn, dear all, sorry for getting involved only so late, but I was too busy with others "things" (sometimes called "work" ;-)) ... Anyway, I just downloaded the MonetDB-4.8.0.tar.gz, extracted it, made BUILD directory, cd'ed to it and ran .../configure --prefix=<MyPrefix> && make && make check where <MyPrefix> is not "/usr" or "/usr/local", but rather a new directory, and that works fine. Then, I re-tried (from newly extracted sources) .../configure && make && make check i.e., using the default prefix "/usr"; make worked fine, but make check immediately killed my desktop ;-) The problem is/was a small tool called "MkillUsers" that come with MonetDB to support Mtest (details on request; they don't matter here...). I just fixed "src/testing/MkillUsers.in" to be less "stupid", and now .../configure && make && make check from the MonetDB-4.8.0.tar.gz works fine for me. We will eventually provide a new source tarball with a bugfix release; for now, just patch your "src/testing/MkillUsers.in" with the attached patch file, i.e., cd MonetDB-4.8.0 patch src/testing/MkillUsers.in < MkillUsers.in.patch Please try again, and let us know, whether it also works for you, now. Note: There seems to be some other problem that appears to be related to the "at" command --- I cannot reproduce it my self, and hence don't know, whether my fix above does solve it. I'll try to investigate this further, and find a solution or work-around. Regards, 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 |
Stefan Manegold wrote:
sorry for getting involved only so late, but I was too busy with others "things" (sometimes called "work" ;-)) ...
No problem, I know this phenomenon 'work' quite well. :) So far I've been getting excellent support for my problems on the list, and I'm happy to be able to help smooth out some kinks in the installation process.
Anyway, I just downloaded the MonetDB-4.8.0.tar.gz, extracted it, made BUILD directory, cd'ed to it and ran
.../configure --prefix=<MyPrefix> && make && make check
where <MyPrefix> is not "/usr" or "/usr/local", but rather a new directory, and that works fine.
Weird, in my case I've supplied my own prefix as well, but that didn't seem to work.
Then, I re-tried (from newly extracted sources)
.../configure && make && make check
i.e., using the default prefix "/usr"; make worked fine, but make check immediately killed my desktop ;-)
:)
The problem is/was a small tool called "MkillUsers" that come with MonetDB to support Mtest (details on request; they don't matter here...). [snip]
I'll try to take a look at this later and report back. Thanks! Regards, Martijn
participants (4)
-
Fabian -
Martijn Faassen -
Niels Nes -
Stefan Manegold