Auto-tools/Goals/2014Q4: Difference between revisions

 
(3 intermediate revisions by 2 users not shown)
Line 48: Line 48:
== Performance ==
== Performance ==


=== Move dzAlerts from Datazilla to Treeherder [ekyle] ===
=== {{missed|}} Move dzAlerts from Datazilla to Treeherder [ekyle] ===


Make dzAlerts (which produces Talos performance regression alerts) ingest data from Treeherder, rather than Datazilla, as the latter doesn't scale well with Talos data.
Make dzAlerts (which produces Talos performance regression alerts) ingest data from Treeherder, rather than Datazilla, as the latter doesn't scale well with Talos data.
Line 54: Line 54:
* {{bug|1092206}}
* {{bug|1092206}}
* Project page: https://wiki.mozilla.org/Auto-tools/Projects/Alerts
* Project page: https://wiki.mozilla.org/Auto-tools/Projects/Alerts
* missed because Treeherder wasn't ingesting all of the Talos performance data, a fact which wasn't obvious until it was too late to address it in time to complete this goal


=== {{defer|}} Create tests for the "charts" (dashboard) service [ekyle] ===
=== {{defer|}} Create tests for the "charts" (dashboard) service [ekyle] ===
Line 102: Line 103:
* Project page: https://mana.mozilla.org/wiki/display/IPPP/GMAIL+Project+Page
* Project page: https://mana.mozilla.org/wiki/display/IPPP/GMAIL+Project+Page


=== {{done|}} Prototype alternate bug views [glob] ===
=== {{miss|}} Prototype alternate bug views [glob] ===


Prototype some alternate bug views which can both decrease page load times and improve the user experience for specific use cases.
Prototype some alternate bug views which can both decrease page load times and improve the user experience for specific use cases.
Line 118: Line 119:
* Project page: N/A
* Project page: N/A


=== Scope the consolidation of non-buildbot tests [bc] ===
=== {{miss|}} Scope the consolidation of non-buildbot tests [bc] ===


We have several separate test suites that run on independent systems, like Autophone, Eideticker, mozbench, power profiling tests, etc.  Each of these requires separate maintenance and feature development.  We will scope the effort involved in consolidating different aspects of these, including test scheduling, test reporting, Android and Firefox OS device maintenance, and the use of buildbot for desktop tests, so we can determine whether or not we should attempt such a consolidation in 2015.
We have several separate test suites that run on independent systems, like Autophone, Eideticker, mozbench, power profiling tests, etc.  Each of these requires separate maintenance and feature development.  We will scope the effort involved in consolidating different aspects of these, including test scheduling, test reporting, Android and Firefox OS device maintenance, and the use of buildbot for desktop tests, so we can determine whether or not we should attempt such a consolidation in 2015.
Line 124: Line 125:
* bug: N/A
* bug: N/A
* Project page: will be created as a deliverable for this work.
* Project page: will be created as a deliverable for this work.
* missed because of work done (by request) to get video tests running in Autophone


=== {{done|}} Make it possible to test mozharness changes on try [armenzg] ===
=== {{done|}} Make it possible to test mozharness changes on try [armenzg] ===
Confirmed users
1,905

edits