On Fri, 2011-07-01 at 23:28 +0200, Chris Kühl wrote:
> On Fri, Jul 1, 2011 at 3:57 PM, Patrick Ohly <[email protected]> wrote:
> > On Fri, 2011-07-01 at 12:24 +0200, Chris Kühl wrote:
> > Another possible difference might be how the script gets invoked. I
> > always run them in the out-of-tree build tree, inside "src". I run with
> >  PATH=.:$PATH <absolute path to source>/test/dbus-test.py
> >
> 
> If I've cleaned my system-wide directories of the syncevolution files
> I find that this doesn't work. I've got to additionally add the
> environment variables for the template and xml files. For me
> specifically it's...
> 
> SYNCEVOLUTION_XML_CONFIG_DIR=/home/chris/checkout/meego/syncevolution/src/syncevo/configs/
> SYNCEVOLUTION_TEMPLATE_DIR=/home/chris/checkout/meego/syncevolution/src/templates/
> PATH=.:$PATH /home/chris/checkout/meego/syncevolution/test/test-dbus.py
> -v

My assumption was that syncevo-dbus-server is compiled and installed
properly. If you want to run without installing, then setting these env
variables is indeed necessary.

When compiling with modules (--enable-shared), then setting
SYNCEVOLUTION_BACKEND_DIR is also necessary.

> > In related news, I updated the test scripts so that D-Bus testing can be
> > run as part of the regular nightly testing, in each of the chroots where
> > tests are run. I triggered a test run, but network problems broke it
> > because the SyncEvolution sources couldn't be updated from gitorious.
> > Otherwise I would have been able now to point to
> > http://runtests.syncevolution.org and reports which contain D-Bus test
> > results.
> >
> 
> This would be very nice to have. Much less chance it'd fall into such
> disrepair if it were run along side the other tests every night.

Exactly.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to