Confirmed users
3,376
edits
m (os cache clearing tip added) |
|||
| Line 28: | Line 28: | ||
=== Testing on Try Server === | === Testing on Try Server === | ||
There are three scenarios that are needed for testing talos on try server: | |||
* Firefox Developer: testing your Firefox changes for performance issues | |||
* Talos Validation: testing your already reviewed and landed patches to the Talos toolchain in production | |||
* Talos Developer: testing patches to Talos which have not been reviewed or landed | |||
For the purposes of Talos development we will ignore the Firefox Developer scenario and discuss the two scenarios regarding Talos toolchain development. In fact, the process is similar for both, lets get started: | |||
First off, you need to edit [[http://dxr.mozilla.org/mozilla-central/source/testing/talos/talos.json?from=talos.json&case=true#1 testing/talos/talos.json]] in your Firefox tree, what is of most importance is: | |||
"talos.zip": { | |||
"url": "http://talos-bundles.pvt.build.mozilla.org/zips/talos.49b74c08dad4.zip", | |||
"path": "" | |||
}, | |||
"global": { | |||
"talos_repo": "https://hg.mozilla.org/build/talos", | |||
"talos_revision": "5e18c3e56875" | |||
} | |||
Android 4.0 tests use "talos.zip:, and all desktop platforms use the "global" section. You can see in global there are 2 fields, "talos_repo" and "talos_revision". | |||
In the scenario where you want to validate Talos, you only need to change "talos_revision" to be the revision of [[http://hg.mozilla.org/build/talos talos]] that your change is. | |||
The same process is used if you want to test a patch prior to review or landing it in the Talos repo. In this case you would edit "global" to look like this: | |||
"global": { | |||
"talos_repo": "http://hg.mozilla.org/users/jmaher_mozilla.com/tpain", | |||
"talos_revision": "default" | |||
} | |||
There are 2 key points here: | |||
* the repo is pointing to a [[https://developer.mozilla.org/en-US/docs/Creating_Mercurial_User_Repositories user repo]] which contains a full copy of the talos repo and all local changes made | |||
* the revision is pointing at "default" | |||
''NOTE: there is a trick with using "default" as the revision, it allows you to check in changes and then retrigger a job on try. This avoids the need to push a new revision to try and wait for a build.'' | |||
Finally if you are validating a push or adjusting something that should or will affect Android Talos, then you need to [[http://hg.mozilla.org/build/talos/file/5e18c3e56875/create_talos_zip.py create a new talos.zip]], ftp that to a people.mozilla.org directory, and then edit the talos.zip section of talos.json to reference it. | |||
Once you have talos.json changed, you just need to select the proper [[http://trychooser.pub.build.mozilla.org/ try chooser]] syntax. | |||
To speed up your development time and everybody else who uses Try server, there is no need to run all tests on all platforms unless this is a major change. Here are some guidelines to follow for testing patches to talos (or dependent modules): | To speed up your development time and everybody else who uses Try server, there is no need to run all tests on all platforms unless this is a major change. Here are some guidelines to follow for testing patches to talos (or dependent modules): | ||