The last 2 weeks I have gone head first into a world of resolving some issues with our mochitest browser-chrome tests with RyanVM, Armen, and the help of Gavin and many developers who are fixing problems left and right.
There are 3 projects I have been focusing on:
1) Moving our Linux debug browser chrome tests off our old fedora slaves in a datacenter and running them on ec2 slave instances, in bug 987892.
These are live and green on all Firefox 29, 30, and 31 trees! More work is needed for Firefox-28 and ESR-24 which should be wrapped up this week. Next week we can stop running all linux unittests on fedora slaves.
2) Splitting all the developer tools tests out of the browser-chrome suite into their own suite in bug 984930.
browser-chrome tests have been a thorn in the side of the sheriff team for many months. More and more the rapidly growing features and tests of developer tools have been causing the entire browser-chrome suite to fail, in cases of debug to run for hours. Splitting this out gives us a small shield of isolation. In fact, we have this running well on Cedar, we are pushing hard to have this rolled out to our production and development branches by the end of this week!
3) Splitting the remaining browser chrome tests into 3 chunks, in bug 819963.
Just like the developer tools, we have been running browser-chrome in 3 chunks on Cedar. With just 7 tests disabled, we are very green and consistently green.
While there are a lot of other changes going on under the hood, what will be seen by next week on your favorite branch of Firefox will be:
- ‘dt’ jobs for opt, and ‘dt1’, ‘dt2’, ‘dt3’ jobs for debug
- ‘bc’ job will turn into ‘bc1’, ‘bc2’, ‘bc3’
- much faster turnaround times on bc tests (62 minutes is the slowest right now, the rest are averaging ~20 minutes/job)
- less random orange cluttering up results