Confirmed users
3,376
edits
Buildbot/Talos/Running: Difference between revisions
→How Talos is Run in Production
(Created page with "= Running Talos Tests = == I have a patch for Talos, what tests to I run? == If you are making changes to talos obviously running the tests locally will be the first step. The...") |
|||
| Line 122: | Line 122: | ||
* [https://tbpl.mozilla.org/ TBPL] receives the name of the suite from buildbot. These are correlated to TBPL letters via http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/tip/js/Config.js . The computed results from graphserver are scraped from the log and displayed when a TBPL suite letter is clicked on in the lower right corner | * [https://tbpl.mozilla.org/ TBPL] receives the name of the suite from buildbot. These are correlated to TBPL letters via http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/tip/js/Config.js . The computed results from graphserver are scraped from the log and displayed when a TBPL suite letter is clicked on in the lower right corner | ||
=== Running Tp the Automation Way === | |||
In our automation, we run beneath many more restrictions than normal users. One of those restrictions is that our automation machines are walled off from the real-world networks. Because of this, and because we want to test pure page-loading and rendering time of Firefox, we serve the pages from localhost using [http://httpd.apache.org/ Apache] thus eliminating all network latency and uncertainty. You've probably noticed this if you looked at the talos/page_load_test/tp4.manifest. | |||
To do this, we construct full downloads of sites in our manifest and they are placed on the automation slave at run time. Because we cannot at this time distribute our full page load test set, I'll walk through how these are set up and show you how to make your own. Note that our next version of the page load set will be distributable, so soon this won't be an issue. | |||
In the meantime, here's the instructions: | |||
<ol> | |||
<li>Use [http://people.mozilla.org/~ctalbert/talos/makepagebundle.sh this script] or, you use the following wget command to fetch a page and everything it links to in order to have a complete page for offline use: <pre> $> wget -p -k -H -E -erobots=off --no-check-certificate -U "Mozilla/5.0 (firefox)" --restrict-file-names=windows --restrict-file-names=nocontrol $URL -o outputlog.txt</pre> | |||
</li> | |||
<li>Once you have a cache of pages, install Apache: <pre> $> sudo apt-get install apache2</pre></li> | |||
<li>Copy your page into the proper location for Apache to serve it. Note that I like to create a page_load_test directory to separate talos from anything else on the webserver. So with Apache defaults, that's something like: <pre> $> mkdir /var/www/page_load_test; cp -R <dir> /var/www/page_load_test/.</pre></li> | |||
<li>Now, add the local URL into your manifest: <pre>http://localhost/page_load_test/<dir></pre></li> | |||
<li>Run the tp tests as above, pointing the config file at your manifest. | |||
</li> | |||
</ol> | |||