[Sugar-devel] Frequent buildbot check failures in sugar-web

[Code Raguet]

>
> 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...


Perhaps we should do as in env.js...
Adding anachronistic unit-tests (tests that check the logic in isolation,
mocking and stubbing the external services and deps) that would run faster,
hence lighting the development process. Also, moving those heavier tests
(whose check through the actual implementation) to another file that,
developers would run after a long round of development (before pushing, for
example) or just leaving that job to buildbot.
Therefore, we would have the benefit that the current tests give (keeping
big timeouts, may be) without delaying developers.


On Fri, Dec 13, 2013 at 2:48 PM, Rogelio Mita <
rogeliomita at activitycentral.com> wrote:

>
> 2013/12/12 Daniel Narvaez <dwnarvaez at gmail.com>
>
>> 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!
>>
>>
> oh!, now we have a lot of information about, let me collect and understand
> better the situation before send a more complete answer
>
>
> --
> Roger
>
> Activity Central <http://activitycentral.com/>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20131213/330ff498/attachment.html>