Re: [Opensync-devel] [trunk] OSYNC_START_TYPE_EXTERNAL example / OSyncClient API changes

[Graham C. <g+o...@co...>]

On Sunday 01 November 2009 13:32:57 Daniel Gollub wrote:
> On Sunday 01 November 2009 01:39:24 am Graham Cobb wrote:
> > 1) When I run the unittests, 17 of them fail.  I don't think any of them
> >  are  related to these changes but is that expected at the moment?
>
> No, actually they should fail.
>
> Could you run: "make Experimental" so the testing resutls get uploaded to
> the CDash dashboard .. so we can have a look on the logs?

I reverted my changes and re-ran the tests.  I got 18 failures.  I ran make 
Experimental but I haven't had time to investigate the failures.  I note that 
most of them failed with:

/home/Linux/opensync/trunk/tests/mock-plugin/mock_sync.c:241:E:mock_write: 
Assertion "!g_file_test(filename, G_FILE_TEST_EXISTS)" failed

Any ideas?

Given that the same errors occur with or without my changes I am going to 
check in my changes anyway.

By the way, I normally only run "make test" as I sort of presumed you didn't 
want the dashboard full of random tests of developers while they are 
debugging their code.  What are the guidelines for when we should run make 
Experimental?

I find the CTest verbose logs fairly uninformative in many cases.  Is there 
any way to use gdb to step through the test case code (and/or to debug the 
OpenSync code)?  

Graham