ReleaseEngineering/BuildFaster: Difference between revisions

← Older edit

ReleaseEngineering/BuildFaster (view source)

Revision as of 21:36, 8 November 2012

466 bytes added , 8 November 2012

→‎Current activities

ChrisCooper

canmove, Confirmed users

2,850

edits

@@ Line 19: / Line 19: @@
 = Current activities =
-Ensure any bugs that are filed for this effort have "buildfaster:pN" in the whiteboard.  Where N is some number 1-5.  P1 is highest priority, P5 is the lowest.
+Ensure any bugs that are filed for this effort have [buildfaster:pN] in the whiteboard.  Where N is some number 1-5.  P1 is highest priority, P5 is the lowest.
-So, our current list of active bugs can be found [https://bugzilla.mozilla.org/buglist.cgi?list_id=743687&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=buildfaster:p here].
+[https://bugzilla.mozilla.org/buglist.cgi?list_id=743687&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=buildfaster:p This is our list of '''current active bugs'''].
-If you'd like to file a bug for something you'd like to see included in this effort, you can use "buildfaster:? in the whiteboard.  These bugs are [https://bugzilla.mozilla.org/buglist.cgi?list_id=743751&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=buildfaster%3A%3F here].
+If you'd like to file a bug for something you'd like to see included in this effort, you can use [buildfaster:?] in the whiteboard.
+[https://bugzilla.mozilla.org/buglist.cgi?list_id=743751&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=buildfaster%3A%3F This is our list of '''proposed bugs'''].
 The table below is for current tasks that are not tracked in bugzilla.
@@ Line 34: / Line 36: @@
 | style="background:#DDD" | '''Status'''
 |-
-| ??
+| {{bug|772446}}
-| Use sdwilsh's notification bot to help devs more easily watch the tree
+| Move all Linux builds to AWS
-| sdwilsh?
+| jhopkins
-| {{StatusHealthy|status=Needs next steps, ctalbert to follow up}}
+| {{StatusHealthy|status=All Firefox builds are there now, just waiting on Thunderbird to catch-up.}}
 |-
-| ??
+| {{bug|758624}}
-| Profile mochitest plain
+| Purchase new machines for win/linux testers that are not tied to aggressive obsolescence schedule
-| jgriffin
+| coop
-| {{StatusHealthy|status=In Progress}}
+| {{StatusBlocked|status=Underway. Various test OSes are being setup and validated.}}
 |-
-| n/a
+| {{bug|784913}}
-| Get data on test run time for each of the moth individual tests
+| migrate linux xpcshell testsuite to AWS
-| ctalbert
+| jmaher
-| {{StatusHealthy|status=COMPLETE}}
+| {{StatusBlocked|status=Blocked on panda work}}
 |-
-| ??
+| {{bug|784913}}
-| Purchase new machines for win/linux builders that are not tied to aggressive obsolescence schedule
+| migrate linux xpcshell testsuite to AWS
-| zandr
+| '''unowned'''
-| {{StatusBlocked|status=Underway, getting gear for lab testing}}
+| {{StatusBlocked|status=Needs an owner}}
 |}
 == Long Term Ideas ==
 * {{bug|657738}} - Automatically determine when oranges happen and auto-star them (no owner/decision on steps yet)
-* {{bug|630534}} - (related) Host tree status outside of tinderbox
+* Windows builds on AWS are still too slow, but we can revisit this regularly
-** This would help us move away from tinderbox and would free up many of the constraints we currently operate under
+* Cross-compile Mac builds on AWS
-* Analyze using VMs for "dial-up" capacity
+** after legal review, *yes* we think we can do this. Need to find a developer owner to give this a try.
-** Would need engineering resources to debug oranges that occur only on vms
+* {{bug|772579}} - Can we run unittests on AWS for Linux (and eventually Windows)?
-** Would need to run some low numbers of vms on an ongoing basis so that we continue to ensure they are providing results we can trust
-** We may need to solve {{bug|617763}} so that these machines can be kept up to date (whether they live in the build VPN or not, i.e. if we use EC2 or something like that...).  Either way we must address the problem that they could be out of date between one dial-in and another dial-in.
 * Analyze methods of understanding and optimizing what we run on a per-checkin basis
 ** Test code related to the current patch?
 ** Run full tests only every x pushes or y time (whichever occurs first).  Between those only run a set of tests related to the patch at hand. (Would need developer override and on-demand testing ability)
 * less frequent debug builds
-* use an optimized xpcshell + httpd.js to run debug tests (depends on {{bug|669953}})
+* use an optimized xpcshell + httpd.js to run debug tests (depends on <s>{{bug|669953}}</s>)
 = Data we need =
 * Profiling on all major harnesses
+** Currently profiling is being done on mochitest harness and tracked [http://brasstacks.mozilla.com/testperf_dashboard/#/mochitest here]. Be sure to select either "opt" or "debug" builds, since choosing "any" is probably not what you want (profiling times differ greatly between the two).
 * How many 10.5-only test failures have there been?  Do we need to run 10.5 tests on-checkin?
 * Where are we spending our time during build slave setup/teardown (catlee owns)
@@ Line 86: / Line 87: @@
 * Joey Armstrong (:joey)
 * Clint Talbert (:ctalbert)
-* Some as-yet undefined set of the A-team (probably Ted, Jmaher and Harth, but I'll put out the call today)
+* Will Lachance (:wlach)
+* Ted Mielczarek (:ted)
+* Chris Cooper (:coop)
 = Definitions =
@@ Line 98: / Line 101: @@
 = Meetings =
-[[ReleaseEngineering/BuildFaster/Meetings/2011-07-07|2011-07-07]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2012-10-11|2012-10-11]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2012-06-28|2012-06-28]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2011-10-26|2011-10-26]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2011-09-28|2011-09-28]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2011-08-31|2011-08-31]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2011-08-17|2011-08-17]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2011-08-03|2011-08-03]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2011-07-20|2011-07-20]]
+* [[ReleaseEngineering/BuildFaster/Meetings/2011-07-07|2011-07-07]]