ReleaseEngineering/BuildFaster/Meetings/2011-07-20: Difference between revisions

ReleaseEngineering/BuildFaster/Meetings/2011-07-20 (view source)

Revision as of 16:51, 20 July 2011

1,948 bytes added , 20 July 2011

→‎Review [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%5Bbuildfaster%3Ap1&list_id=704087 [buildfaster:p1]] bugs

Mdas

Confirmed users

561

edits

@@ Line 22: / Line 22: @@
 == Review [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%5Bbuildfaster%3Ap1&list_id=704087 [buildfaster:p1]] bugs ==
+* {{bug|367393}}
+**Still picking out parts of packed.js while rewriting some of the useful functions.
+** Finding which tests have dependencies on packed.js and instead depend on the respective parts of MochiKit.
+* {{bug|479352}} - backed out,  ctalbert to help figure out what the issue is with m1 tests
+* {{bug|561754}} - waiting on the server to be set up for sending the symbol processing to.  Re-casting the related talos bug so that it's clear what the solution is there and moving it to talos component as talos work is required to enable this functionality.
+** Blocked - Waiting for [?] to show up. Moving to talos component.
+* {{bug|623617}}
+** Has working prototype set up. Wiki pages will be set up regarding changes
+* {{bug|658313}}
+** Finishing up Talos changes to allow PGO builds. Should be ready for review shortly. Currently working for mozilla-central
+** Worried about slave capacity from running the extra every-4-hour PGO builds
+*** Ties up one slave per platform per branch per day
+*** Can we run PGO only on nightly builds instead?
+*** If we do only nightly PGO builds, maybe use Try for bisecting if we hit a failure?
+** Should make sure that TBPL distinguishes PGO vs. non-PGO builds on the same changeset to avoid confusion and notice PGO-specific test failures
+* {{bug|659328}}
+** Working on a patch that needs some refactoring, should be up for next week
+* {{bug|669930}}
+** samliu is working on getting data dumps and displaying metrics properly
+* {{bug|669988}}
+** motivation was faster build times from doing single-arch builds; we're getting new build hardware soon, so this may not be an issue. -> p5
+* {{bug|670229}}
+** Need to distinguish between tests that are slow (>10s) and tests that are supposed to take a longer time
+** Someone should look at each test and see if there's no obvious reason for it being slow, file bugs on those
+** See if certain tests are much slower on debug, hard to give a good heuristic
 == Review [[ReleaseEngineering/BuildFaster#Current_activities|current activities]] ==