[Sugar-devel] Frequent buildbot check failures in sugar-web
Rogelio Mita
rogeliomita at activitycentral.com
Tue Dec 24 11:15:02 EST 2013
https://github.com/sugarlabs/sugar-web/pull/102
2013/12/12 Daniel Narvaez <dwnarvaez at gmail.com>
> Right, as expected
>
>
> 1386897905.351919 DEBUG root: IndexStore.flush: force=True _pending_writes=0
> 1386897905.352442 DEBUG root: Start database flush
> 1386897909.310487 DEBUG root: Completed database flush
> 1386897909.334923 DEBUG root: FileStore: Nothing to do
>
>
> Only on the first save().
>
> Using *getEnv*().*defaultTimeoutInterval* = something we could increase the timeout for all the datastore tests or even for all the tests. I'm worried it would get a bit annoying for development to always have a big timeout... An alternative could be to have a speficic test at the top to get through this, with a title explaining what it's doing, so that we wouldn't keep breaking it. I dunno... thoughts? Patches welcome too, if anyone has more time than me!
>
>
--
Roger
Activity Central <http://activitycentral.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20131224/9a5ac953/attachment.html>
More information about the Sugar-devel
mailing list