Turning off these tests is not an option given how large percentage of the B2G test body they represent. I've started sending some feelers to see if I can find an owner.
Other than v1.1 blockers, getting in better shape with regards to testing should be our top priority, so avoiding removing tests should be at the top of that list. Given the fact that the failing code here appears to be the marionette code itself (unless I'm misunderstanding the bug), I had assumed that this fell on the a-teams responsibility. Not sure if that's incorrect or not? / Jonas On Wed, Jul 31, 2013 at 8:02 AM, Ryan VanderMeulen <[email protected]> wrote: > On 7/25/2013 11:10 AM, Fabrice Desre wrote: >> >> Tests are not in great shape either, and sheriffs are considering to >> hide the B2G Marionnette tests later today due to the ongoing high >> failure rate >> >> (https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&short_desc=socket.timeout&resolution=---&query_format=advanced&short_desc_type=allwordssubstr&list_id=7335976) > > > FYI, I will be hiding the Marionette WebAPI test suite on m-c (and feeder > branches) on Friday since apparently nobody on the B2G team is going to own > getting them to satisfy our job visibility policy [1]. > > If someone wants to take ownership, bug 898074 is tracking the main source > of failures. > > -Ryan > > [1] https://wiki.mozilla.org/Sheriffing/Job_Visibility_Policy > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
