Confirmed users
353
edits
Auto-tools/Meetings/2012-06-11: Difference between revisions
Jump to navigation
Jump to search
→Goals Progress
| Line 7: | Line 7: | ||
** [jgriffin] - Turned on mochitest-plain on the B2G continuous-integration system: {{bug|759887}}. Need to investigate some random failures which are causing chunks to fail to start. | ** [jgriffin] - Turned on mochitest-plain on the B2G continuous-integration system: {{bug|759887}}. Need to investigate some random failures which are causing chunks to fail to start. | ||
* {{miss| | * {{ok|Provide generic interfaces/web app plugability for new harnesses to reuse the same infrastructure backend}} | ||
** [jeads|carljm|camd] We can now create new datazilla projects in an automated fashion. This includes building an object store and performance database to collect json objects and index them in an RDBS schema. Once a project is created, it can be posted to immediately. This is available for testing on Mozilla-MPT vpn. Contact jeads or carljm if you need to start a project. | |||
* {{miss|Ensure that new UI is based on extensible statistics package that can be used both by developers and the graphserver UI.}} | |||
** [jeads] This goal was deferred in favor of new goal to detect regression per push. This doesn't mean there is no UI for datazilla, there is a "stock" UI available that allows you to examine all data submitted. We stopped extending it in mid April to concentrate on setting up a system that can detect a performance regression in an automated fashion. | |||
* {{ok|Signal From Noise Phase II - Make the same noise-reduction changes we made on Tp5 on all the other page-load tests and ensure all performance tests are sending raw observations to Datazilla.}} | * {{ok|Signal From Noise Phase II - Make the same noise-reduction changes we made on Tp5 on all the other page-load tests and ensure all performance tests are sending raw observations to Datazilla.}} | ||