Revision as of 20:54, 28 June 2011

Previous Action Items

[DONE] Investigate next steps for Flash content tests (bug 635310). (Anthony)
[CARRY OVER] Implement a 'max memory' view to expose testruns consuming large amounts of memory. (Dave)
[CARRY OVER] Schedule endurance test involvement for next Mozmill testday. (Dave/Henrik)
[CARRY OVER] Investigate if we can gather all details from about:support in the same way that we currently gather metrics from about:memory. (Dave)
[CARRY OVER] [UNASSIGNED] Investigate diagnostic interfaces to all systems.
- What can we gather?
- How can we sync this data up?
[CARRY OVER] Investigate extra resources for endurance tests. (Matt)
[CARRY OVER] Investigate caching results to disk during testrun to reduce any impact on memory metrics (bug 634580). (Dave)
[DONE] Cancel next meeting due to PTO. (Dave)
[DONE] Fix the failing test. (Dave)
[DONE] Raise a new bug for dealing with issues encountered when gathering metrics (bug 661245). (Dave)

[ASSIGNED] bug 635310 - Mozmill Endurance test for flash video performance - ashughes
- Currently reaching out to Benoit Girard and Chris Jones to get more detailed information about Flash rendering
- Prelim: video, ads, and games each use different rendering methods -- will likely mean 3 separate tests
Running an endurance test with restarts enabled and a large number of iterations causes Disconnect Error bug 658395 - patches in review.

@@ Line 5: / Line 5: @@
 = Previous Action Items =
-* {{prev|Investigate next steps for Flash content tests ({{bug|635310}}). (Anthony)}}
+* {{done|Investigate next steps for Flash content tests ({{bug|635310}}). (Anthony)}}
 * {{prev|Implement a 'max memory' view to expose testruns consuming large amounts of memory. (Dave)}}
 * {{prev|Schedule endurance test involvement for next Mozmill testday. (Dave/Henrik)}}