Le 18/12/2013 16:55, Dale Harvey a écrit : > setTimeout is not bad because it is async, it is bad because it is non > deteministic, async tests can and are reliable. Mochitests are some of > the most stable on tbpl and heavily use async api's, just never expect > that an action can be done given an arbitrary timeout, have a way for > being notified or determining that the action is complete
The main issue is that using setTimeout or other async tests on Travis and TBPL will always trigger intermittent from time to time because it will hit the max timeout for a test. So sometimes we can't avoid it, and in that case we should augment the expected timeout, but we should try hard to not use async tests if it's possible.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
