MozillaWiki

ReleaseEngineering/TryServer

< ReleaseEngineering
Revision as of 11:19, 28 February 2013 by Pnkfelix (talk | contribs) (→‎Try Server: We should include a tbpl link in the overview.)

Try Server

The try server is an easy way to test a patch without actually checking the patch into the core repository. Your code will go through the same tests as a mozilla-central push, and you'll be able to download builds if you wish.

To use try server, you need a Mozilla hg account (level 1 is sufficient).

How to push to try

Gecko 15-17 note

Try has switched to Pymake, so it won't normally work with Gecko 15-17 Win32 builds. To make Try work for those builds, add this patch to your queue.

Running a subset of builds/test/talos available to Try

You must use Build:TryChooser to choose which builds, tests, and talos you would like run on your push to try. Make sure you place the try chooser text in your topmost commit. The TryChooser web page can help you build a commit message for custom requests, so can the mercurial extension 

% hg qref --message "try: -b o -p all -u all -t none"
% hg push -f try

Pushing to try

To submit your changes to the try server (assuming they're modifications to mozilla-central or a similar branch, e.g. tracemonkey), you have a few options:

Creating an alias

To save yourself some typing, you can add an alias to your hgrc: 

[paths]
try = ssh://hg.mozilla.org/try

and then push with 

hg push -f try

~/.ssh/config

ssh host settings to make life easier 

Host hg.mozilla.org
  User <commit_user_email_address>
  IdentityFile ~/.ssh/alternate_public_identity_key_file

hg phases

hg phases were introduced in Mercurial 2.1. Their purpose is to keep you from accidentally modifying changesets you've shared with others, or from accidentally sharing your patch queue with others. In particular, this keeps you from qpop'ing patches you've pushed to try!

When you run hg qpop after pushing to try, you'll get 

abort: popping would remove an immutable revision

You can force hg to let you qpop your patch queue by running 

hg phase -f --draft qbase:tip

Disable hg phases with a post-push hook

Alternatively, you can avoid this rigamarole by disabling hg phases with an outgoing hook. Add the following to your personal .hgrc file (~/.hgrc): 

 [hooks]
 post-push = hg phase --force --draft "mq()"

Now you should be able to perform hg push -f <whatever> without it affecting the phase.

These extra steps should no longer be necessary once the server is upgraded to Mercurial 2.1 and configured as "non-publishing" (bug 725362).

If you use an alias (e.g. "hg try" instead of "hg push -f ssh://hg.mozilla.org/try")

If you use an alias (e.g. you use hg try to push to try), this won't work -- you need to actually specify the post-command that you want it to perform after.

For example, if you alias your push command to hg try, as 

  [alias]
  try = push -f ssh://hg.mozilla.org/try

Then you need to use the following instead of the above post-push hook: 

[hooks]
post-try = hg phase --force --draft "mq()"

Viewing the results

You can see the results of your tryserver build in a number of ways:

  • You'll get an email on a successful push with a link to tbpl for your revision as well as emails on any non-successful build/test/talos results (this setting can be adjusted using Build:TryChooser args for email notification)
  • You can have the results of your try run posted to bug(s) automatically at the completion of the run using the --post-to-bugzilla flag in your try syntax (see: Build:TryChooser for examples)
  • Look for your changeset on Try TBPL. You can add &pusher=YOUR.EMAIL to only see your pushes.
  • Compare Talos perf numbers using Pike's talos-node or mconnor's compare-talos.
  • Download your completed builds from firefox/tryserver-builds on ftp.m.o.

If you're using Mercurial queues, the push -f command pushes any patches that are currently applied, and the Try server will build the result. (This is an awesome feature, not a bug!)

You don’t need to clone or pull from the try repo, and you probably don’t want to. You’d get every half-baked changeset anybody ever tested.

See Jorendorff's blog for more details.

Using a custom mozconfig

The mozconfigs for recent mozilla-central clones are located in the browser/config/mozconfigs directory. Edit those as you please.

(Android mozconfigs are in mobile/android/config/mozconfigs or mobile/xul/config/mozconfigs.)

Note:

  • TryServer purpose is to tell what will happen on Tinderbox, not to check every possible build option/configuration.
    • Any non-standard feature is implicitly unsupported. You may try them, but don't complain if they break.

Old crufty way

For revisions prior to around Oct 4, 2011, you'll be using the default buildbot-configs based mozconfigs, and will need to add some extra files to your push.

If you want to use setting other than those in the default mozconfigs, you can push an extra file to the $topsrcdir:

  • mozconfig-extra with settings to be applied to all mozconfigs
  • mozconfig-extra-$platform to apply changes only to that platform's mozconfig, where $platform is one of linux, linux64, win32, macosx, macosx64, linux-android, maemo5-gtk, maemo5-qt

The options you enable/disable in your custom mozconfig are appended to the existing config.

The default mozconfigs used for tryserver builds are available in Hg: http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/$platform/try (linux example)

Using older GCC

Linux and Linux64 build bots are using GCC 4.5 for Try builds. But some branches will fail to build or run tests with this version of GCC because of the libstdc++ dependency it adds. Such branches are those where bug 643690 hasn't landed. If you want to push such a branch to Try, you need to add the following to mozconfig-extra-linux and/or mozconfig-extra-linux64 in the top directory: 

CC=/tools/gcc-4.3.3/installed/bin/gcc
CXX=/tools/gcc-4.3.3/installed/bin/g++

How to get non-PGO coverage

A lot of the following is out of date, see: https://wiki.mozilla.org/ReleaseEngineering/TryChooser#What_if_I_want_PGO_for_my_build

On branches where bug 643704 has landed, adding the following in a mozconfig-extra or mozconfig-extra-$platform file will suffice: 

mk_add_options MOZ_PGO=

On other branches, fool the system!

Include this in your patch. 

diff --git a/client.mk b/client.mk
--- a/client.mk
+++ b/client.mk
@@ -210,5 +210,5 @@ else
 endif

-profiledbuild::
+Xprofiledbuild::
        $(MAKE) -f $(TOPSRCDIR)/client.mk build MOZ_PROFILE_GENERATE=1
        $(MAKE) -C $(PGO_OBJDIR) package
@@ -352,5 +352,5 @@ endif
 # Build it

-build::  $(OBJDIR)/Makefile $(OBJDIR)/config.status
+profiledbuild::  $(OBJDIR)/Makefile $(OBJDIR)/config.status
        $(MOZ_MAKE)

Server Status

Other Notes

HOWTO: Preserve a commit message between try pushes

Simply create a new patch in your queue for the try attempt commit message. Future pushes can simply push/pop the try patch onto the applied queue when needed. 

% hg qref --message "bug xxx - a spell/patch of improvements"
% hg qnew patch.try
% hg qpush patch.try
% hg qref --message "try: -b o -e -p all -u all -t none"
% hg push -f try
% hg qpop patch.try

Other Mozilla Try Servers

Problem Diagnosis

Test your account & configuration

  • ssh hg.mozilla.org, response: "No Interactive shells allowed here!"
  • ssh hg.mozilla.org clone invalid_sandbox, response: menu display and interactive prompting.

Buildduty issues

How do I trigger additional talos/test runs for a given try build?

See ReleaseEngineering/How_To/Trigger_Talos_Jobs

How do I cancel existing jobs?

TBD

TryChooser

See the TryChooser wiki page.

Bug Commenter

This is on cruncher and is run in a crontab in lsblakk's account: 

source /home/lsblakk/autoland/bin/activate && cd /home/lsblakk/autoland/tools/scripts/autoland \
&& time python schedulerDBpoller.py -b try -f -c schedulerdb_config.ini -u None -p None -v

You can see quickly if things are working by looking at: 

/home/lsblakk/autoland/tools/scripts/autoland/postedbugs.log  # this shows what's been posted lately
/home/lsblakk/autoland/tools/scripts/autoland/try_cache  # this shows what the script thinks is 'pending' completion

See Also

Retrieved from "https://wiki.allizom.org/index.php?title=ReleaseEngineering/TryServer&oldid=532233"