33
edits
Auto-tools/Meetings/2012-07-02: Difference between revisions
→Goals Progress
| Line 6: | Line 6: | ||
* {{done|Datazilla: Provide generic interfaces/web app plugability for new harnesses to reuse the same infrastructure backend}} | * {{done|Datazilla: Provide generic interfaces/web app plugability for new harnesses to reuse the same infrastructure backend}} | ||
** We now have error-tracking in place that will make it easier to track down issues with data we are getting from test harnesses. | |||
* {{done|Datazilla: Ensure that new UI is based on extensible statistics package that can be used both by developers and the graphserver UI.}} | * {{done|Datazilla: Ensure that new UI is based on extensible statistics package that can be used both by developers and the graphserver UI.}} | ||
** ''NOTE:'' Revised deliverable in light of developer feedback and changed course mid-quarter to deliver a system that would turn TBPL orange/green based on per-patch regression detection, this means we won't deliver the UI by end of quarter, but we'll still land datazilla on production hardware in end of Q2/early Q3 (waiting on hardware to arrive) | ** ''NOTE:'' Revised deliverable in light of developer feedback and changed course mid-quarter to deliver a system that would turn TBPL orange/green based on per-patch regression detection, this means we won't deliver the UI by end of quarter, but we'll still land datazilla on production hardware in end of Q2/early Q3 (waiting on hardware to arrive) | ||
*** Hardware has arrived, IT is working on setting everything up, security review meeting will be this week. | |||
* {{done|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.}} | * {{done|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.}} | ||