to easily reproduce :

*(master)*greg@brutus:~/Documents/Projets/shinken/test$ *git checkout -b
test_livestatus*
Switched to a new branch 'test_livestatus'
*(test_livestatus)*greg@brutus:~/Documents/Projets/shinken/test$

*(test_livestatus)*greg@brutus:~/Documents/Projets/shinken/test$ *git revert
-n 0c626cd00a3fcfc18562e7dd66e9ea54464820fa *
Finished one revert.
*(test_livestatus)*greg@brutus:~/Documents/Projets/shinken/test$

*(test_livestatus)*greg@brutus:~/Documents/Projets/shinken/test$
*./test_livestatus.py
TestConfigSmall.test_status *


and you'll directly get the assertion error.


greg.



Le 17 février 2011 13:39, Grégory Starck <g.sta...@gmail.com> a écrit :

> Hi,
>
> for now (well for some days unfortunately) I'm on a specific problem ; the
> one with livestatus that I encountered when I made the commit
>  8113605b5652e3273ada9287b785c56f1b857bf7  &
>  0c626cd00a3fcfc18562e7dd66e9ea54464820fa
>
> but after long debugging  it seems the problem would be because the
> test_livestatus doesn't fork for the livestatus module ; and as far as I see
> that brings python object mix problem : the Service object is thus twice
> instanciated :  one normal time by scheduler ; and one time by livestatus
> (by manage_initial_service_status)   but when livestatus relink the downtime
> it so relinks the downtime with its own Service object which is not the one
> from scheduler.. then scheduler gets this bad relink of the downtime to a
> Service object not the same as initially.. and that would makes the problem
> here..
>
> (I hope I'm quite clear, if not I'll re-explain)
>
> So I'm not sure if there is really an error with livestatus module or if
> it's not the test_livestatus that should be adapted in some way..
>
> wdyt ??
>
> greg.
>
>
>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel

Reply via email to