Confirmed users
1,927
edits
Auto-tools/Projects/peptest: Difference between revisions
Jump to navigation
Jump to search
→Further Work: telemetry
(→Further Work: telemetry) |
|||
| Line 164: | Line 164: | ||
{{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). | {{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). | ||
=== Telemetry histograms === | |||
Capturing telemetry information would be useful in diagnosing causes of responsiveness. Results would be available after running a test, and by clicking through on the stats UI. | |||
=== Integration with SPS === | === Integration with SPS === | ||
| Line 171: | Line 175: | ||
=== Mozmill e10s === | === Mozmill e10s === | ||
''' Note: this will likely be put on hold indefinitely until the status of e10s becomes more clear ''' | '''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. | 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. | ||