That's good to hear! I'll wait for now. Though if the fixes aren't imminent (let's say a month or more out), then it might still be worth unscheduling them for the time being and doing the work on try. I'd be happy to provide guidance for this if this is a path you want to explore.
On 08/03/16 11:31 AM, Benjamin Francis wrote:
Hi Andrew, Please hold off on this. I understand Dylan Oliver is discussing this with Chris AtLee. We're figuring out what to do with test infrastructure as part of the B2G OS transition project, including how to continue to support the TV team who will branch 2.6 off mozilla-central later this year for product releases. Thanks Ben On 8 March 2016 at 16:09, Andrew Halberstadt <[email protected] <mailto:[email protected]>> wrote: I recently filed bug 1254531 [1] to track unscheduling b2g jobs on trunk branches to save AWS resources. They are all currently busted: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-tier=3 Because these jobs are all scheduled in-tree via taskcluster, *they can be re-scheduled by pushing to try*. This means if anyone wants to work on re-enabling them, they can do so directly on try. If there is already imminent work underway that will green up these jobs, please let me know and I can hold off. Otherwise, there isn't really any reason to leave them running on trunk branches. Please let me know if there are any reasons I shouldn't proceed! Cheers, Andrew [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1254531 _______________________________________________ dev-fxos mailing list [email protected] <mailto:[email protected]> https://lists.mozilla.org/listinfo/dev-fxos
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
