Confirm
709
edits
Changes
Remove a b2g example
The [https://wiki.mozilla.org/ReleaseEngineering/TryServer TryServer] is a critical piece of our infrastructure for ensuring that patches are suitable for landing prior to being pushed. However, proper usage is important to avoid pushing under- or over-tested patches. This page is intended to provide some recommended practices for finding the right balance. The [http://trychooser.pub.build.mozilla.org/ TryChooser Syntax Builder] offers control over which builds and tests are run.
Note that the guidelines below are not a substitute for using your best judgementjudgment. The guidelines below are intended to be general recommendations but not absolute musts.
<ol>
<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.
<ul><li>For example, a B2GLinux-only Try run should look something like "try: -b do -p emulatorlinux,emulator-jblinux64,emulatorlinux64-kk,linux32_gecko,linux64_gecko,macosx64_gecko,win32_gecko pgo -u all -t none"</li></ul>
</li>
<li>Be aware of which test suites are likely to be affected by your patch and avoid running others that won't.</li>
