Sheriffing/How To/Beta simulations

Beta Simulations

Helpful tip: To have a more accessible command when pushing to try, open the .hgrc file and below the [alias] line add trymc = push -f ss://hg.mozilla.org/try
Open the doc with the past beta simulations and known issue Version X, at this point Version 64 https://docs.google.com/document/d/1zOgJc1_6DF7j78WTU7Ai1dWSv-A1RU563M8A3AGlU5A/edit# - Request access if you are new to this.
Add the new day for which you’re making the simulation by copying the entry for the last day and modifying the date.

Go to mozilla-central, take the HG link from the latest central push and add it as a base revision in the document.

TRUNK AS EARLY BETA

Open the Trunk as Early Beta link from the document. This will have at least 2 changesets.

• Click on the second revision from the top which shall have ‘Base Config’ in the description - this will send you to the try mercurial link of the changeset - then copy the RAW link (upper part of the page).
• Open the console and run the following commands:
  • hg pull central
  • hg update central
  • hg qqueue -c central-beta //creates a new queue with the name “central-beta” to which you will add the patches. The hg qq command lets you work with different patch series. Because the patches for central as beta simulations shall be reused and also be prevented from accidentally getting pushed to an integration or release repo, it makes sense to use it here. If you ALREADY HAVE A QUEUE you can just use hg qqueue central-beta to move to the queue you’re using for the beta-sim
  • hg qimport <raw_link> -n base_config//import the base config patch with raw_link being its address copied earlier and “base_config” the name in queue
  • hg qpush//temporarily activate the patch in the queue
• Move on to the second changeset from the Trunk as Early Beta link from the previous simulation from the document, the Trunk as Early Beta link.

• Same as for base_config, we will need the Raw Link from the Trunk as Early Beta revision, and we will follow these commands:
  • hg qimport <raw_link> -n early_beta
  • hg qpush
• Follow this flow for as many changesets as you need to.
• After everything was qimported and qpushed, we can now push to try: hg trymc if you use the alias, OR hg push -f ssh://hg.mozilla.org/try if you do not have an alias set.

Open the first Treeherder link in the console. It might take a few minutes for Treeherder to find that job, though. Add the link after you deselect the running and the green jobs and check that the classified jobs are visible, in the current date section at Run Links: Trunk as Early Beta in the Gdoc.

TRUNK AS LATE BETA

Go to the console and use the following commands:

• hg qimport <raw_link> -n late_beta
• hg qpush
• hg trymc OR hg push -f ssh://hg.mozilla.org/try

Add the link in the document after you deselect running and green jobs, in the current date section at RUN LINKS Trunk as Late Beta.
Also, in the New Bugs Section - you can write TBD (“To Be Done”) until the jobs on your try pushes have ran and you can see if there are failures or not. NOTE: When creating a bug, add tracking only for permafails. Low frequent intermittents or frequent intermittents also affecting mozilla-central don’t need that flag but should be created and not be added to the Google Doc about the simulations.

When done, switch back to your usual queue:

• hg qpop -a //empty the queue
• hg qqueue patches//switch to the default queue patch
• hg qqueue -l//to check that you are not in the central-as-beta queue anymore

After the beta simulations are done:

• Remove the “TBD” from the bug list for today’s simulations if there is no new failure and replace it with “None”
• If there were known issues before the beta simulations which you didn’t fix with a backout or patch import and which are gone, open those bugs (should be “Resolved Fixed”) and set the status_firefox<version number> to “verified” and change “Resolved Fixed” to “Verified Fixed”. Also add a comment that it has been verified fixed and add the link to today’s simulation.

When we need to add a backout:

• hg qbackout -esr/er <raw_link_from_backout> -n <bug_number>//The revisions of the bug whose backout fixes the issue.

VERSION INCREASE SIMULATION

To verify if a certain failure occurs in an increased beta-sim version, you need to open the gdoc and search for a previous Version Increase link.
In your console create a new queue (gecko_version_increase) and import the raw link from the Version increase link from the doc.

• hg qimport <raw_link> -n version_increase
• hg qpush
• hg trymc