|
|
| Line 48: |
Line 48: |
| 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". | | 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. | | In the Talos Validation scenario, 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:
| | For the Talos Developer scenario, you would edit "global" to look like this: |
| "global": { | | "global": { |
| "talos_repo": "http://hg.mozilla.org/users/jmaher_mozilla.com/tpain", | | "talos_repo": "http://hg.mozilla.org/users/jmaher_mozilla.com/tpain", |
| Line 65: |
Line 65: |
|
| |
|
| Once you have talos.json changed, you just need to select the proper [[http://trychooser.pub.build.mozilla.org/ try chooser]] syntax. | | 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):
| |
|
| |
| * If you patch touches one file and is very minor, get minimal testing on it (1 mobile test, 1 windows test, local testing): try: -b o -p win32,android -u none -t svgr,remote-tsvg
| |
| * If you patch affects setup of the tests (config or profile) or launching of the process and is very minimal, get minimal testing on it (1 mobile test, 1 windows test, local testing): try: -b o -p win32,android -u none -t svgr,remote-tsvg
| |
| * If your patch changes a test (add or edit), test that test locally (remember a new test will need graph server changes and buildbot changes)
| |
| * If your patch changes mobile testing, test all mobile tests and 1 desktop test: (There is no good current way of doing this with try; I recommend two try runs:
| |
|
| |
| try: -b o -p win32 -u none -t svgr
| |
|
| |
| try: -b o -p android -u none -t all
| |
|
| |
| )
| |
| * If your patch changes results or output processing, run ts, tp5 on mobile, windows and locally: try: -b o -p win32,android -u none -t tpn,chromez,remote-ts,remote-tp4m_nochrome
| |
| * If your patch changes any import statement (or code referenced in the import), please test on windows, linux, and mobile as these all run different versions of python: try: -b o -p linux,win32,android -u none -t all
| |
| * If your patch changes a lot of stuff around, if you are not sure, or if you are going to deploy a new talos.zip, it is strongly recommended to run all talos tests: try: -b o -p all -u none -t all
| |
|
| |
| If you are reviewing a talos patch, it is your responsibility to recommend the proper testing approach. If you think it needs more than these guidelines, call it out. If it needs less, call it out also.
| |
|
| |
|
| == Are my numbers ok == | | == Are my numbers ok == |