Use Try? Read this.

Two updates to Try are about to go into effect which enforce asking for what you want using the try syntax and configuring how much email you want to get with your results.  Read more below.

Bug 661409 – Now that this has landed, a push to try only generates email about a particular try builder’s results if it does not succeed.  You can adjust this to be more verbose by adding a -e/–all-emails to your try syntax if you miss getting over all those emails, or you can just shut off the emails completely with a -n/–no-emails in your commit syntax. Note that you must be using the “try: ” syntax for these email flags to be picked up which leads quite handily to…

Bug 649402 – Try syntax use is about to be mandatory as soon as this bug is fixed and the hg hook is enabled on the try repo. We’re doing this to encourage developers who use try to take an extra moment and request only the resources they absolutely need on their push.  This should reduce the test/talos load that has been increasing wait times across all branches during busy periods.  One additional psychological change is that the “try: -a” syntax has been removed and in order to ask for a mozilla-central matching run you must be more explicit: “try: -b do -p all -u all -t all”. I’ve updated the docs to reflect this change as well as the TryChooser syntax helper webpage. We’re really not trying to make your life harder with this change, approximately 50-60% of pushes to try currently use the try syntax and if you push to try without it you will get a helpful message pointing you to docs and syntax builder.  Check with #developers for tips and tricks from the folks who’ve been using this since the beginning, I know they have many including using the newly-minted Mozilla-Inbound repo where a push will get the complete set of tests/talos if you’d like to let your patch bake for a bit after doing a selective try run.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.