Investigating some unit test failures I am seeing a lot of setTimeout's located inside the tests, someone already made a meme for me for the occasion
http://mozillamemes.tumblr.com/post/24322890551/now-if-you-add-an-event-listener-that-sets-a More specifically everyone is gonna have a bad time because we will have buggy intermittent tests and closed trees, just a reminder for coders and more specifically reviewers that setTimeouts should pretty much only be used to yield / spin the event loop inside tests, not for any form of timer / waiting solution Cheers Dale _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
