4:45 a.m.
On Do, 2011-06-23 at 16:57 +0200, Chris Kühl wrote:
Ok, I did this and it seems to sync fine after starting the
dbus-http-server.
You shouldn't have to start it. test-dbus.py itself (re)starts the
daemon for each test.
To be explicit here is what I'm doing step-by-step...
1) From the hacking document, I'm building using make ./autogen.sh
&& ./configure
--with-synthesis-src=/home/chris/checkout/meego/libsynthesis/
--enable-dbus-service --disable-shared --enable-libcurl
--enable-unit-tests --enable-developer-mode && make -j4
2) I then install to /usr/local/. (I'm aware one should be able to run
the static binary from the source tree. I'll do this once I'm confident
things are working.)
3) Add a D-Bus-Testing address book in evolution and make sure my
Memotoo account works.
4) Run syncevolution --configure --template Memotoo username=<your
username> password=<your password> database=D-Bus-Testing dbus_unittest
addressbook
6) Run syncevo-http-server http://localhost:9000/syncevolution &
7) Test that it's working using syncevolution dbus_unittest (The failed
but told me how to fix it)
8) Change the server variable in test/test-dbus.py
to /usr/local/libexec/syncevo-dbus-server
You should be able to avoid this by setting your PATH variable so that
it contains your self-compiled syncevo-dbus-server.
9) Go into the test folder and run ./test-dbus.py
Does this seem correct?
I'm puzzled by the need to start the daemon manually.
When running ./test-dbus.py (from where I branched, commit
cfa5f08a31c),
the test finishes without giving me useful results other than the final
tally. I was expecting a report of some kind. The end of the output to
the console looks like this...
There should be an error report for each failed test. Use test-dbus.py
-v for more information as tests are run. This is standard Python unit
testing.
=========================================================================
server output:
[INFO] /usr/local/libexec/syncevo-dbus-server: ready to run
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Wed Jun 22 16:27:06 2011, duration 0:00min |
| fatal error (remote, status 500) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: error code from SyncEvolution fatal error
(remote, status 500): addressbook: addressbook: no such address book:
'SyncEvolution_Test_addressbook_1'
This is part of the output for one failed tests. Scroll up to see which
one. Output for a failed test can be very large, because it includes
dumps of the syncevo-dbus-server stdout and from dbus-monitor.
Are there other script to run or test sources to create for this to
succeed?
The nightly testing turns this output into HTML, but you don't need
that.
--
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.