Confirmed users
1,927
edits
Auto-tools/Projects/peptest: Difference between revisions
Jump to navigation
Jump to search
statistics and reporting
(statistics and reporting) |
|||
| Line 154: | Line 154: | ||
* --server-path: This must be set to the path to a directory serving as the root of the local web server. | * --server-path: This must be set to the path to a directory serving as the root of the local web server. | ||
* --proxy-host-dirs: This indicates that the files in the web server root should be organized according to URL. Without this option, the same content, as found in the server path, is served for all proxied URLs. With this option, the web server root should have one directory per URL. See peptest/tests/firefox/server/ for an example of how the server root should be structured when --proxy-host-dirs is given (as used in buildbot). | * --proxy-host-dirs: This indicates that the files in the web server root should be organized according to URL. Without this option, the same content, as found in the server path, is served for all proxied URLs. With this option, the web server root should have one directory per URL. See peptest/tests/firefox/server/ for an example of how the server root should be structured when --proxy-host-dirs is given (as used in buildbot). | ||
== Peptest Statistics == | |||
Peptest is run automatically as part of buildbot. The results are gathered and displayed at http://mrcote.info/peptest/ (temporary URL; eventually they will be folded into the next version of the graph server/perfomatic). At the moment, peptest is run only on try; it will soon be expanded to mozilla-central, mozilla-inbound, and possibly other branches. | |||
== Further Work == | == Further Work == | ||
=== | === Automatic reports === | ||
{{bug|737886}} has been filed to set up reporting when significant deviations occur in buildbot's peptest results. Since we can't develop a simple pass/fail result, developers will have to rely on these reports to determine when responsiveness has gotten worse (or better). | |||
=== Integration with SPS === | === Integration with SPS === | ||
| Line 167: | Line 169: | ||
For each function wrapped in a performAction() call, we should enable the profiler, so we can tell where each action spent its time. We can use [https://developer.mozilla.org/en/Performance/Profiling_with_the_Built-in_Profiler SPS] to this end. This is filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=706847 bug 706847]. | For each function wrapped in a performAction() call, we should enable the profiler, so we can tell where each action spent its time. We can use [https://developer.mozilla.org/en/Performance/Profiling_with_the_Built-in_Profiler SPS] to this end. This is filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=706847 bug 706847]. | ||
=== | === Mozmill e10s === | ||
''' Note: this will likely be put on hold indefinitely until the status of e10s becomes more clear ''' | |||
Mozmill doesn't use MessageManager when it interacts with content. This means that it will not work correctly with Electrolysis builds (which is mostly the entire point of Peptests). Mozmill will need to be refactored to use MessageManager and also to stop using the gBrowser object which doesn't exist in mobile Firefox. | |||
== Related Bugs == | == Related Bugs == | ||