Confirmed users
3,816
edits
Auto-tools/Projects/Futurama/Draft Plan: Difference between revisions
Auto-tools/Projects/Futurama/Draft Plan (view source)
Revision as of 17:12, 4 December 2012
, 4 December 2012→Solve Immediate term capacity problems
(Created page with "So, the plan is two fold. We aim to lay foundations for future automation improvements at the same time as fixing immediate-term issues in the overall automation problem space. S...") |
|||
| Line 4: | Line 4: | ||
=== Solve Immediate term capacity problems === | === Solve Immediate term capacity problems === | ||
* Get Linux tests running in VMs to improve our current linux wait times, and free up real linux hardware to be repurposed for windows jobs | * Get Linux tests running in VMs to improve our current linux wait times, and free up real linux hardware to be repurposed for windows jobs | ||
** Needs changes to OF/Tbpl/LogParser/etc so that we can track intermittent issues and filter them by machine name/type (list of issues only happening on vms/hardware) | ** Needs changes to OF/Tbpl/LogParser/etc (can we make it so it's sustainable to add new platforms in the future (perhaps a version 1.5 vs. 2)) so that we can track intermittent issues and filter them by machine name/type (list of issues only happening on vms/hardware) | ||
* Regenerate the goFaster dashboards to understand where our performance bottlenecks are and to monitor them for regressions/improvements as we make changes to the overall build/test automation | * Regenerate the goFaster dashboards to understand where our performance bottlenecks are and to monitor them for regressions/improvements as we make changes to the overall build/test automation | ||
* Complete work to have manifests on mochitests so that all test harnesses have '''some kind''' of manifest file so that we can more easily change the set of tests we are running based on various conditions (i.e. type of machine - vm or hardware) without having to code in those changes to makefiles | * Complete work to have manifests on mochitests so that all test harnesses have '''some kind''' of manifest file so that we can more easily change the set of tests we are running based on various conditions (i.e. type of machine - vm or hardware) without having to code in those changes to makefiles | ||