>Is there a user-visible problem? >What you show here is that the automated testing fails because it doesn't >expect the update on the client, >but that doesn't necessarily mean that something bad happened during the sync. No user-visible problem.
>Which test is it that fails? testComplexUpdate >Does it work with SyncEvolution? If yes, what is the difference in the data >exchange with the server? Yes, SyncEvolution works well. In SyncEvolution, after client updated it's contact then synced with google server, client sent its changes, no changes from google. But in Buteo, google also sent updated items which is not a real change, google sent the same item as client sent to it. -----Original Message----- From: Ohly, Patrick Sent: Friday, November 12, 2010 8:28 PM To: Miao, Qiankun Cc: [email protected]; [email protected] Subject: RE: [MeeGo-dev] strange behavior when sync Buteo with Google contacts On Fr, 2010-11-12 at 11:46 +0000, Miao, Qiankun wrote: > >To really clean the Google side of sync, use the script which we use > in the nightly SyncEvolution testing. It uses the Google data web API. > Yes, I do clean google. Then I don't know why the server behaves like that. > >I'm not sure I understand. What exactly is the problem (expected vs. real > >outcome)? > +---------------|-----------------------|-----------------------|-CON-+ > | | LOCAL | REMOTE | FLI | > | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS | > +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ > | ./contacts | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | > | two-way, 0 KB sent by client, 0 KB received | > +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+ > ----------|--------CLIENT---------|--------SERVER---------| > | NEW | MOD | DEL | NEW | MOD | DEL | > ----------|-----------------------------------------------| > Expected | 0 | 0 | 0 | 0 | 1 | 0 | > > You can refer log file in fail.tar.gz for more detail. Is there a user-visible problem? What you show here is that the automated testing fails because it doesn't expect the update on the client, but that doesn't necessarily mean that something bad happened during the sync. Which test is it that fails? Does it work with SyncEvolution? If yes, what is the difference in the data exchange with the server? -- 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. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
