[Xapian-devel] Build problems
olly at survex.com
Tue Feb 13 10:11:46 GMT 2007
On Tue, Feb 13, 2007 at 09:53:31AM +0000, James Aylett wrote:
> On Tue, Feb 13, 2007 at 08:19:18AM +0000, Olly Betts wrote:
> > I've just checked, and the current state is that the cached databases
> > are deleted when a particular backend is selected. The consequence
> > is that you shouldn't really encounter this problem, except in
> > the case where the ".flint" databases are hosed or an older version and
> > you run apitest with "-b remotetcp" or "-b remote", which uses the
> > databases in ".flint" (you can do this implicitly with "make check-remote").
> > If you weren't doing that, I can't see how it failed...
> The automatic stuff runs with -b remotetcp and -b remote at various
> points, doesn't it? It mean, it says it's running with remotetcp and
> remote, and that's when it failed...
If you run "make check", then no -b option is passed and all backends
which are enabled are used, but flint is run before remote and remotetcp
so the .flint directory should be up to date.
Hmm, I wonder if the issue is remotetest not apitest. That gets run
before apitest, but probably relies on .flint being up to date.
Really remotetest should just be merged into apitest at this point. It
used to be separate mostly because apitest didn't test the remotetcp
backend, but it now does. I'll sort that out.
> > Nuking on failure is problematic, since it prevents you inspecting the
> > database which can be helpful in working out why a test failed.
> Suppress nuking on -v?
Perhaps, though I'm not sure -v should do more than give more output.
> > Perhaps ixion actually ran out of VM or processes?
> > What was the actual error message apitest gave?
> I can't remember in detail, but I think it was something like
> "couldn't find 'Listening' in output".
That probably means that xapian-tcpsrv failed to start cleanly. There's
not much more we can do if that happens AFAICS.
More information about the Xapian-devel