Confirmed users
79
edits
Auto-tools/Projects/Platform Quality/External Media Tests: Difference between revisions
Auto-tools/Projects/Platform Quality/External Media Tests (view source)
Revision as of 21:15, 18 March 2016
, 18 March 2016→Automation Information: Further pf-jenkins information
(→Automation Information: Further pf-jenkins information) |
|||
| Line 62: | Line 62: | ||
** *-e10s - job that is run with e10s enabled e.g. m-e10s, y-e10s | ** *-e10s - job that is run with e10s enabled e.g. m-e10s, y-e10s | ||
** *-bw - tests that runs for various bandwidths | ** *-bw - tests that runs for various bandwidths | ||
=== Debugging === | |||
You can RDC/VNC to individual machines in pf-jenkins. (User: mozilla). When there are problems, it often helps to trigger the job from pf-jenkins, and watch it run in your VNC window. You can also launch a mozilla-build shell and run scripts yourself. You should avoid running from the Jenkins workspace directories; you should be able to get the necessary assets to reproduce the tests on a directory on the local drives. | |||
Command-lines for jobs can be found in the pf-jenkins GUI by selecting the project and either reading through the logs, or going into the configure pane, copying, and then pasting into your shell window. | |||
=== Custom Profile === | |||
Netflix and network bandwidth limiting tests use a stored profile with custom logins and certificates installed. | |||
* Windows: c:\testing\eme_profile | |||
* Mac: /Users/mozilla/testing/eme_profile | |||
=== How to disable an individual failing test on pf-jenkins. === | === How to disable an individual failing test on pf-jenkins. === | ||