On Mon, 2011-11-07 at 14:09 +0100, Thomas Pequet wrote:
> Hello Patrick
> 
> Strange all theses problem ...
> 
> I have difficult to understand your log because there is no XML with 
> SyncML ...
> Can you add the XML ?

You can find the corresponding logs by going up one level. Let me walk
you through an example.

http://syncev.meego.com/2011-11-04-16-43_all/testing-amd64/20-memotoo/Client_Sync_eds_event_testRefreshStatus.log

http://syncev.meego.com/2011-11-04-16-43_all/testing-amd64/20-memotoo
has all *.log files and the corresponding session directory. Each
session has the Synthesis HTML log file and the corresponding XML
message dumps, linked to from the HTML log file with "saved as" links.

In Client_Sync_eds_event_testRefreshStatus.log there were two sessions:

[DEBUG 00:00:04] 1. starting 
Client_Sync_eds_event_testRefreshStatus.refresh-from-client.client.A with sync 
mode refresh-from-client
=> 
http://syncev.meego.com/2011-11-04-16-43_all/testing-amd64/20-memotoo/Client_Sync_eds_event_testRefreshStatus.refresh-from-client.client.A/

[DEBUG 00:00:17] 2. starting 
Client_Sync_eds_event_testRefreshStatus.two-way.client.A with sync mode two-way
=> 
http://syncev.meego.com/2011-11-04-16-43_all/testing-amd64/20-memotoo/Client_Sync_eds_event_testRefreshStatus.two-way.client.A/

The second session did not finish as expected. From the .log file:

[INFO 00:00:25] sync report:
+---------------|-----------------------|-----------------------|-CON-+
|               |         LOCAL         |        REMOTE         | FLI |
|        Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
|     eds_event |  0  |  1  |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
|     two-way, 0 KB sent by client, 0 KB received                     |
|     item(s) in database backup: 1 before sync, no backup after it   |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
|          start Sat Nov  5 10:41:00 2011, duration 0:08min           |
|               synchronization completed successfully                |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
----------|--------CLIENT---------|--------SERVER---------|
          |  NEW  |  MOD  |  DEL  |  NEW  |  MOD  |  DEL  |
----------|-----------------------------------------------|
Expected  |    0  |    0  |    0  |    0  |    0  |    0  |
Expected sync mode: two-way


Zero modified items were expected for the client, but one was modified
during the session.

You can compare this against eds_contact in that same test run, against
other servers in the same run
(http://syncev.meego.com/2011-11-04-16-43_all/testing-amd64/nightly.html)  or 
against the older test done at the time when SyncEvolution 1.2 was released 
(http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-2/syncev.meego.com/2011-10-13-11-59_all_syncevo=syncevolution-1-2-branch/head-testing-amd64/nightly.html)

It would be nice to convert the .log text files into .html with
hyperlinks. Perhaps I'll add 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.


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

Reply via email to