Mercurial > hg > audiodb
view tests/0017/run-test.sh @ 509:cc2b97d020b1
Code rearrangements to tease apart library code from C++ audioDB code.
There should be precisely no functional changes in this commit.
Instead, the only thing that has happened is that all the abstraction
violation and other horribleness is concentrated in one place: the
include of "audioDB-internals.h" in audioDB.h -- the separation will be
complete once that include can be removed.
This include is necessary because the command-line binary / SOAP server
still does some things directly rather than through an API: not least of
which the operations that have not yet been integrated into the API yet,
but also some messing around with constants, flags and nominally
internal functions. The intent is to remove as many of these as
possible and think quite hard about the rest.
In the meantime, the library is now much more self-contained: the only
things it uses are in the audioDB_API.h and audioDB-internals.h headers;
thus there are fewer nasty surprises lurking for readers of the code.
The Makefile has been adjusted to take advantage of this rearrangement
in the dependencies.
author | mas01cr |
---|---|
date | Thu, 15 Jan 2009 13:57:33 +0000 |
parents | fe4dc39b2dd7 |
children |
line wrap: on
line source
#! /bin/bash . ../test-utils.sh if [ -f testdb ]; then rm -f testdb; fi ${AUDIODB} -d testdb -N # tests that the lack of -l when the query sequence is shorter doesn't # segfault. intstring 2 > testfeature floatstring 0 1 >> testfeature floatstring 1 0 >> testfeature ${AUDIODB} -d testdb -I -f testfeature # sequence queries require L2NORM ${AUDIODB} -d testdb -L start_server ${AUDIODB} 10017 echo "query point (0.0,0.5)" intstring 2 > testquery floatstring 0 0.5 >> testquery # FIXME: this actually revealed a horrible failure mode of the server: # since we were throwing exceptions from the constructor, the # destructor wasn't getting called and so we were retaining 2Gb of # address space, leading to immediate out of memory errors for the # /second/ call. We fix that by being a bit more careful about our # exception handling and cleanup discipline, but how to test...? expect_client_failure ${AUDIODB} -c localhost:10017 -d testdb -Q sequence -f testquery expect_client_failure ${AUDIODB} -c localhost:10017 -d testdb -Q sequence -f testquery -n 1 check_server $! echo "query point (0.5,0.0)" intstring 2 > testquery floatstring 0.5 0 >> testquery expect_client_failure ${AUDIODB} -c localhost:10017 -d testdb -Q sequence -f testquery expect_client_failure ${AUDIODB} -c localhost:10017 -d testdb -Q sequence -f testquery -n 1 check_server $! # see if the server can actually produce any output at this point ${AUDIODB} -c localhost:10017 -d testdb -Q sequence -l 1 -f testquery -n 1 > testoutput echo testfeature 0 0 1 > test-expected-output cmp testoutput test-expected-output stop_server $! exit 104