Confirmed users
3,990
edits
User:Armenzg/Test pool efficiency: Difference between revisions
User:Armenzg/Test pool efficiency (view source)
Revision as of 18:47, 28 September 2015
, 28 September 2015reboots and from job to job
(runner dashboard) |
(reboots and from job to job) |
||
| Line 14: | Line 14: | ||
** checkout | ** checkout | ||
== About reboots == | |||
We always reboot on Windows testers since runner isn't managing all the processes there. We also reboot after any android, emulator, mochitests or reftests, since those change the system state in ways we haven't been able to identify...the only way to get back to a known good state is to reboot. | We always reboot on Windows testers since runner isn't managing all the processes there. We also reboot after any android, emulator, mochitests or reftests, since those change the system state in ways we haven't been able to identify...the only way to get back to a known good state is to reboot. | ||
Reboots can happen as part of runner (post mozharness run) or as part of mozharness. | |||
== From job to job == | |||
Finish job --> reboot (mh or runner) --> bootup --> runner does pre-flight checks, | |||
including running clobber --> starts buildbot | |||
We do know when machines run buildbot again if runner is in place since it reports to influxdb. | |||
NOTE: bootup !== aws slave spinup time | |||
= Known bugs = | = Known bugs = | ||