canmove, Confirmed users
1,126
edits
Sheriffing/How To/Recommended Try Practices: Difference between revisions
Sheriffing/How To/Recommended Try Practices (view source)
Revision as of 14:54, 25 August 2015
, 25 August 2015Update machine time per push
(Bug 1082602) |
(Update machine time per push) |
||
| Line 4: | Line 4: | ||
<ol> | <ol> | ||
<li>In many cases, a "try: -b do -p all -u all -t none" is overkill and <b>should be avoided</b>. A full Try run consumes <b><u>over | <li>In many cases, a "try: -b do -p all -u all -t none" is overkill and <b>should be avoided</b>. A full Try run consumes <b><u>over 500hrs of machine time</u></b> to generate a full set of builds and run the full suite of tests across them. This can have a real impact on wait times across resource-constrained platforms, including production runs.</li> | ||
<li>If in doubt, run both debug and opt builds.</li> | <li>If in doubt, run both debug and opt builds.</li> | ||
<li>If the patch only affects one platform, only that platform should have builds and tests. | <li>If the patch only affects one platform, only that platform should have builds and tests. | ||