ReleaseEngineering/BuildFaster/Meetings/2011-08-31: Difference between revisions
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
== Action items from last time == | == Action items from last time == | ||
* jgriffin to | * will to follow up with catlee regarding dashboard calculations | ||
* jgriffin to change test run comparison routine to compare against a range of recent m-c runs instead of one run to help mitigate the fact that test durations vary considerably per run, even when equivalent | |||
* | * jgriffin to get data on infrequently failing tests, and how long they take to run | ||
* | * ted to file bug about harnesses downloading symbols on demand | ||
* Any [https://bugzilla.mozilla.org/buglist.cgi?list_id=935439&resolution=---&status_whiteboard_type=anywordssubstr&query_format=advanced&status_whiteboard=buildfaster%3Ap2%20buildfaster%3Ap3%20buildfaster%3Ap4%20buildfaster%3Ap5 p2] bugs need to escalate? | * Any [https://bugzilla.mozilla.org/buglist.cgi?list_id=935439&resolution=---&status_whiteboard_type=anywordssubstr&query_format=advanced&status_whiteboard=buildfaster%3Ap2%20buildfaster%3Ap3%20buildfaster%3Ap4%20buildfaster%3Ap5 p2] bugs need to escalate? | ||
Revision as of 23:09, 30 August 2011
Details
August 17, 2011 @ 9am PDT / 12pm EDT
dial-in x92 304
Backchannel #buildfaster on irc.mozilla.org
Agenda
- Dashboard site is live and fast now (thanks to wlach); what do all the numbers mean?
- related to above, where are we w.r.t our 2-hour goal? Which open items are going to produce the greatest improvements?
- Review the Action Items & Bugs
Action items from last time
- will to follow up with catlee regarding dashboard calculations
- jgriffin to change test run comparison routine to compare against a range of recent m-c runs instead of one run to help mitigate the fact that test durations vary considerably per run, even when equivalent
- jgriffin to get data on infrequently failing tests, and how long they take to run
- ted to file bug about harnesses downloading symbols on demand
- Any p2 bugs need to escalate?
Review [buildfaster:p1] bugs
Review current activities
- we've put investigation of running debug tests with opt xpcshell on hold, since opt debug builds seem likely to materialize sometime soon (bug 669953)
- still need a mechanism to track individual slow tests; jmaher suggested the correct metric to do this is test duration/test asserts; need to update the logparser to handle this