81633bc6771b8b26a943c4ea9179ed8ff8bb8d35: Merge mozilla-central to b2g-inbound
Carsten "Tomcat" Book <cbook@mozilla.com> - Mon, 16 Feb 2015 16:25:41 +0100 - rev 243073
Push 702 by wcosta@mozilla.com at Tue, 17 Feb 2015 14:44:33 +0000
Merge mozilla-central to b2g-inbound
29673996d54b42e74bc105a6d12a758930c202b8: Bumping manifests a=b2g-bump
B2G Bumper Bot <release+b2gbumper@mozilla.com> - Mon, 16 Feb 2015 07:01:40 -0800 - rev 243072
Push 702 by wcosta@mozilla.com at Tue, 17 Feb 2015 14:44:33 +0000
Bumping manifests a=b2g-bump
2eeb2e87eae959a99c50dbb48309f596a030a972: Bumping gaia.json for 2 gaia revision(s) a=gaia-bump
B2G Bumper Bot <release+b2gbumper@mozilla.com> - Mon, 16 Feb 2015 06:59:07 -0800 - rev 243071
Push 702 by wcosta@mozilla.com at Tue, 17 Feb 2015 14:44:33 +0000
Bumping gaia.json for 2 gaia revision(s) a=gaia-bump ======== https://hg.mozilla.org/integration/gaia-central/rev/051a02e5a248 Author: Timothy Guan-tin Chien <timdream@gmail.com> Desc: Merge pull request #28201 from timdream/gaia-toast Bug 1129817 - Land gaia-toast, r=wilsonpage ======== https://hg.mozilla.org/integration/gaia-central/rev/36ec82662f21 Author: Timothy Guan-tin Chien <timdream@gmail.com> Desc: Bug 1129817 - Land gaia-toast
7077823cbada87b6022b45fd720c16620acb0ce9: Bug 674779 - Merging cpow measurements and own/system time measurements draft
David Rajchenbach-Teller <dteller@mozilla.com> - Tue, 17 Feb 2015 11:32:22 +0100 - rev 243070
Push 701 by dteller@mozilla.com at Tue, 17 Feb 2015 10:33:08 +0000
Bug 674779 - Merging cpow measurements and own/system time measurements
f7b0f8e0b98e2efc0afac41437ca05ccc1c384ab: Bug 674779 - Per-CPU compartment accounting (own and total time) draft
David Rajchenbach-Teller <dteller@mozilla.com> - Mon, 19 Jan 2015 17:02:07 +0100 - rev 243069
Push 701 by dteller@mozilla.com at Tue, 17 Feb 2015 10:33:08 +0000
Bug 674779 - Per-CPU compartment accounting (own and total time)
7089d487d565fc771641c0df605a6ea27a5e8772: Bug 674779 - Per-CPU compartment accounting draft
David Rajchenbach-Teller <dteller@mozilla.com> - Thu, 15 Jan 2015 15:00:13 +0100 - rev 243068
Push 701 by dteller@mozilla.com at Tue, 17 Feb 2015 10:33:08 +0000
Bug 674779 - Per-CPU compartment accounting
5097812509ff9eef03ae7d4c59626db885e0dbbd: Bug 674779 - Reset the performance stop watch whenever we process the next event on a worker draft
David Rajchenbach-Teller <dteller@mozilla.com> - Thu, 15 Jan 2015 14:48:02 +0100 - rev 243067
Push 701 by dteller@mozilla.com at Tue, 17 Feb 2015 10:33:08 +0000
Bug 674779 - Reset the performance stop watch whenever we process the next event on a worker
37f66b645ed5fcd5584c63c5e6559f0e827e95b5: Bug 674779 - Reset the performance stop watch whenever we process the next event draft
David Rajchenbach-Teller <dteller@mozilla.com> - Thu, 15 Jan 2015 14:47:49 +0100 - rev 243066
Push 701 by dteller@mozilla.com at Tue, 17 Feb 2015 10:33:08 +0000
Bug 674779 - Reset the performance stop watch whenever we process the next event
d355b8fdac928dc8aa8de32933e672e1ee45251a: Bug 1132771 - Implement file-info mach command draft
Gregory Szorc <gps@mozilla.com> - Mon, 16 Feb 2015 15:45:19 -0800 - rev 243065
Push 700 by gszorc@mozilla.com at Mon, 16 Feb 2015 23:45:44 +0000
Bug 1132771 - Implement file-info mach command Now that we have a mechanism for defining file-based metadata, let's add a mach command to interface with it. The mach allows people to easily see which metadata is defined on which files. There is also an execution mode that prints a list of arguments missing Bugzilla metadata. This will help people identify which files still need annotated.
30292697274c8189cc7e58e16310e5979fd50c04: Bug 1132771 - Define some bug components draft
Gregory Szorc <gps@mozilla.com> - Mon, 16 Feb 2015 14:36:16 -0800 - rev 243064
Push 700 by gszorc@mozilla.com at Mon, 16 Feb 2015 23:45:44 +0000
Bug 1132771 - Define some bug components This patch defines bug components for code that I have historically touched.
15d26058a1e2274baa1c09be6f3785f5846c86c1: Bug 1132771 - Add FILES to moz.build with ability to define Bugzilla component draft
Gregory Szorc <gps@mozilla.com> - Mon, 16 Feb 2015 14:27:07 -0800 - rev 243063
Push 700 by gszorc@mozilla.com at Mon, 16 Feb 2015 23:45:44 +0000
Bug 1132771 - Add FILES to moz.build with ability to define Bugzilla component Now that we can obtain relevant contexts from file paths, we introduce our first consumer of this API: the FILES variable. FILES is a dictionary of file matching patterns to metadata for matching files. e.g. you say "for all .cpp files in a directory, define the attribute X." We implement the "bug_component" attribute. This attribute is a 2-tuple (actually a named tuple) defining the Bugzilla product and component for files. There are no consumers yet. But we eventually want to enable things like "suggest a bug component for the patch I just wrote."
60b6da165f340573de4043f1ff2d234b1a878fbd: Bug 1132771 - Add FILES to moz.build with ability to define Bugzilla component draft
Gregory Szorc <gps@mozilla.com> - Mon, 16 Feb 2015 12:29:56 -0800 - rev 243062
Push 699 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:36:14 +0000
Bug 1132771 - Add FILES to moz.build with ability to define Bugzilla component Now that we can obtain relevant contexts from file paths, we introduce our first consumer of this API: the FILES variable. FILES is a dictionary of file matching patterns to metadata for matching files. e.g. you say "for all .cpp files in a directory, define the attribute X." We implement the "bug_component" attribute. This attribute is a 2-tuple (actually a named tuple) defining the Bugzilla product and component for files. There are no consumers yet. But we eventually want to enable things like "suggest a bug component for the patch I just wrote."
2d1445a2917a4b20b4193dd041263e243d34b750: Bug 1132771 - Add a test for reading all moz.build files in file metadata mode draft
Gregory Szorc <gps@mozilla.com> - Thu, 12 Feb 2015 19:03:15 -0800 - rev 243061
Push 699 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:36:14 +0000
Bug 1132771 - Add a test for reading all moz.build files in file metadata mode XXX TODO THIS IS NOT THE CORRECT APPROACH XXX
2ee14ae2c5de704ebebc7300fee734aedec67f64: Bug 1132771 - Optionally don't export variables when reading moz.build files draft
Gregory Szorc <gps@mozilla.com> - Thu, 12 Feb 2015 18:58:37 -0800 - rev 243060
Push 699 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:36:14 +0000
Bug 1132771 - Optionally don't export variables when reading moz.build files Exporting the same variable twice in a stack of traversals results in an error. Since we don't need exported variables when in manual moz.build traversal mode, add an option to disable it and disable it in our manual traversal mode.
4615cd746fe4b974f6ce283b8fdb72bbbc02dc23: Bug 1132771 - Define source flags next to source files in moz.build draft
Gregory Szorc <gps@mozilla.com> - Thu, 12 Feb 2015 18:43:21 -0800 - rev 243059
Push 699 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:36:14 +0000
Bug 1132771 - Define source flags next to source files in moz.build We were failing to evaluate moz.build files in the new directory hierarchy based traversal mode because of a KeyError attempting to manipulate a source file that isn't defined on this platform. Fix the problem but putting the .flags adjustment in the same block as the definition of the source file.
ad2e491ba9d070687dd2d8a9bc8952915b17e524: Bug 1132771 - Support explicit directory traversal of moz.build files draft
Gregory Szorc <gps@mozilla.com> - Thu, 12 Feb 2015 18:11:21 -0800 - rev 243058
Push 699 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:36:14 +0000
Bug 1132771 - Support explicit directory traversal of moz.build files This patch teaches moz.build files how to traverse/descend with an arbitrary directory mapping, ignoring any traversal values embedded within *DIRS files. Using this new behavior is an API to read moz.build files relevant for a set of input filenames. We eventually plan to use this new API to read metadata from moz.build files relevant to a set of files, possibly just one file. There are still improvements to this implementation. While not tested, I'm almost entirely confident that traversal on mozilla-central will fail. Also, we will likely want to use a dummy config object so we can traverse without having build context. We should ideally be able to traverse on a fresh source checkout.
59bcec1e3464a8b67d88313fd524c86e82d85a9e: Bug 1132771 - Provide a back door to disable reading of GYP files draft
Gregory Szorc <gps@mozilla.com> - Thu, 12 Feb 2015 17:03:33 -0800 - rev 243057
Push 699 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:36:14 +0000
Bug 1132771 - Provide a back door to disable reading of GYP files We'll be introducing functionality that processes moz.build files slightly differently. In this new mode, we don't care about GYP files. Add a flag to disable the processing of GYP files.
eadbe4abd606e2aa1867091f98bc799801de05cb: Bug 1132771 - API to return moz.build files relevant for a set of paths draft
Gregory Szorc <gps@mozilla.com> - Thu, 12 Feb 2015 23:15:12 -0800 - rev 243056
Push 699 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:36:14 +0000
Bug 1132771 - API to return moz.build files relevant for a set of paths We have an eventual goal to store file-level metadata in moz.build files and to have this metadata "cascade" down directory hierarchies. e.g. metadata in the root directory will apply to all children directories. A prerequisite for this feature is a way to query which moz.build files are relevant to a given file. In this patch, we implement an API that returns this information.
e4c63a798768183183c767db920761f267f34c62: Bug 1132771 - Allow setter functions in FlagsFactory draft
Gregory Szorc <gps@mozilla.com> - Mon, 16 Feb 2015 11:27:11 -0800 - rev 243055
Push 699 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:36:14 +0000
Bug 1132771 - Allow setter functions in FlagsFactory Advanced use cases of FlagsFactory may wish to perform additional data verification at attribute set time. This patch introduces a mechanism to allow setter functions to be declared for individual flags on FlagsFactory instances. The use case for this feature is to perform additional verification or type coercion at variable assignment time. For example, we may wish to convert a generic tuple into a dedicated type.
d9e060dde9a775d921c2bd137bc35aec2c40a935: Bug 1132771 - Add FILES to moz.build with ability to define Bugzilla component draft
Gregory Szorc <gps@mozilla.com> - Mon, 16 Feb 2015 12:29:56 -0800 - rev 243054
Push 698 by gszorc@mozilla.com at Mon, 16 Feb 2015 20:34:37 +0000
Bug 1132771 - Add FILES to moz.build with ability to define Bugzilla component Now that we can obtain relevant contexts from file paths, we introduce our first consumer of this API: the FILES variable. FILES is a dictionary of file matching patterns to metadata for matching files. e.g. you say "for all .cpp files in a directory, define the attribute X." We implement the "bug_component" attribute. This attribute is a 2-tuple (actually a named tuple) defining the Bugzilla product and component for files. There are no consumers yet. But we eventually want to enable things like "suggest a bug component for the patch I just wrote."
(0) -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip