021aea3c1eecbac89b30fdf4f1340f5224148c29: Bug 1348981 - provide method to re-initialize URLPreloader for xpcshell tests r?kmag draft
Robert Helmer <rhelmer@mozilla.com> - Thu, 21 Sep 2017 11:24:14 -0700 - rev 668497
Push 81068 by bmo:rhelmer@mozilla.com at Thu, 21 Sep 2017 19:11:43 +0000
Bug 1348981 - provide method to re-initialize URLPreloader for xpcshell tests r?kmag MozReview-Commit-ID: rnjEJc1Uir
0d246a16d32bd8d2d540f10e9b72f5f74a772b69: Bug 1348981 - add Cu.readURI helper for sync file reading on startup r?kmag draft
Robert Helmer <rhelmer@mozilla.com> - Tue, 19 Sep 2017 12:13:08 -0700 - rev 668496
Push 81068 by bmo:rhelmer@mozilla.com at Thu, 21 Sep 2017 19:11:43 +0000
Bug 1348981 - add Cu.readURI helper for sync file reading on startup r?kmag MozReview-Commit-ID: 1yz25afCUDs
5a77ae795e2f0623664fe3cc40320e96658e671d: Bug 1348981 - provide a list of valid system add-ons for packaging r?glandium draft
Robert Helmer <rhelmer@mozilla.com> - Wed, 13 Sep 2017 22:49:43 -0700 - rev 668495
Push 81068 by bmo:rhelmer@mozilla.com at Thu, 21 Sep 2017 19:11:43 +0000
Bug 1348981 - provide a list of valid system add-ons for packaging r?glandium MozReview-Commit-ID: K2jCHBBJBqw
3f0597c9004fad2de8eec727c97bf085fd3ab165: Bug 1033395 - Panels Should Be Anchored from the Same Height on the Toolbar. r?Gijs draft
Erica Wright <ewright@mozilla.com> - Wed, 13 Sep 2017 15:49:32 -0400 - rev 668494
Push 81067 by bmo:ewright@mozilla.com at Thu, 21 Sep 2017 19:05:03 +0000
Bug 1033395 - Panels Should Be Anchored from the Same Height on the Toolbar. r?Gijs MozReview-Commit-ID: 6bhlfeD1esE
1db6cade014a423573440f017b9c71b9236dd27b: Bug 1402069 - Add a test string for the new localization API. draft
Zibi Braniecki <zbraniecki@mozilla.com> - Thu, 21 Sep 2017 19:55:17 +0200 - rev 668493
Push 81066 by bmo:gandalf@aviary.pl at Thu, 21 Sep 2017 18:52:39 +0000
Bug 1402069 - Add a test string for the new localization API. MozReview-Commit-ID: KhCW1n9LDka
0b604bc8d0862a653c341a26b3c7511750b3df16: Bug 1347798 - Create a small per-document bindings for DOMLocalization. r?mossop draft
Zibi Braniecki <zbraniecki@mozilla.com> - Sat, 09 Sep 2017 19:23:03 -0700 - rev 668492
Push 81066 by bmo:gandalf@aviary.pl at Thu, 21 Sep 2017 18:52:39 +0000
Bug 1347798 - Create a small per-document bindings for DOMLocalization. r?mossop MozReview-Commit-ID: DfxIYVxyt9C
9c0d96a08d8f04800b62df947584effcced704d3: Bug 1387415 - Make toolbarspring elements drag handles for the window. draft
Sam Foster <sfoster@mozilla.com> - Thu, 21 Sep 2017 09:28:55 -0700 - rev 668491
Push 81065 by bmo:sfoster@mozilla.com at Thu, 21 Sep 2017 18:48:42 +0000
Bug 1387415 - Make toolbarspring elements drag handles for the window. * Define a new binding for toolbarspring elements which adds window-dragging behavior. * Apply -moz-window-drag: drag property to toolbarspring elements. This enables a fast-path for platforms that have CSS window drag support (windows, OSX). MozReview-Commit-ID: 8ZABYMWswk1
8d29a05600bfadc5f592bd6973efdd3d4124af36: Bug 1402010 - Support not reading test manifests in moz.build files; r?chmanchester draft
Gregory Szorc <gps@mozilla.com> - Thu, 21 Sep 2017 11:40:08 -0700 - rev 668490
Push 81064 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:41:04 +0000
Bug 1402010 - Support not reading test manifests in moz.build files; r?chmanchester Not all consumers of moz.build evaluation are interested in test manifest data. Normally, processing it isn't a big deal so we just do it. However, there are a few scenarios where this is difficult. The difficulty processing test manifests stems from the fact that test manifest parsers aren't part of the mozbuild Python package. The Python modules are defined elsewhere in the repo. In the case of reading moz.build files from version control, a full checkout may not be available or the calling process may not be running from the specific revision being evaluated. In either case, these manifest processing modules may not be available and moz.build evaluation will fail. This commit introduces a flag on BuildReader.files_info() to control whether test manifests are loaded. If disabled, an evaluation flag is added and when the respective moz.build variables are evaluated, they see the flag and short-circuit. The module imports in testing.py were also refactored as part of this change to swallow any import failure. We had previously delay imported these modules as a way to work around the import failure in certain context. If the import fails, an exception will be thrown attempting to operate on None. This is slightly more annoying than an explicit ImportError. The reason we can't keep the import in the function is because "import" is processed at block scoping, so if an import is in a block, it gets processed, even if that line is never evaluated. Various callers not needing to access test manifest data have been changed to not load it. A side effect of this change is that various `mach file-info` commands became faster! For example, `mach file-info bugzilla-component 'testing/**'` dropped ~500ms from ~9000ms. MozReview-Commit-ID: 9mtBg4AWCc
18645ca015fbf32206c957a152ffaf045fe41bcb: Bug 1402059 - Don't import editBookmarkOverlay.js in places.xul on Mac because it is imported elsewhere. r?florian draft
Mark Banner <standard8@mozilla.com> - Thu, 21 Sep 2017 19:35:04 +0100 - rev 668489
Push 81063 by bmo:standard8@mozilla.com at Thu, 21 Sep 2017 18:37:54 +0000
Bug 1402059 - Don't import editBookmarkOverlay.js in places.xul on Mac because it is imported elsewhere. r?florian MozReview-Commit-ID: 5e32dMnLdik
74dd02043e00065649486bffe96dc00659b02427: Bug 1402010 - Support not reading test manifests in moz.build files; r?chmanchester draft
Gregory Szorc <gps@mozilla.com> - Thu, 21 Sep 2017 11:31:34 -0700 - rev 668488
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1402010 - Support not reading test manifests in moz.build files; r?chmanchester Not all consumers of moz.build evaluation are interested in test manifest data. Normally, processing it isn't a big deal so we just do it. However, there are a few scenarios where this is difficult. The difficulty processing test manifests stems from the fact that test manifest parsers aren't part of the mozbuild Python package. The Python modules are defined elsewhere in the repo. In the case of reading moz.build files from version control, a full checkout may not be available or the calling process may not be running from the specific revision being evaluated. In either case, these manifest processing modules may not be available and moz.build evaluation will fail. This commit introduces a flag on BuildReader.files_info() to control whether test manifests are loaded. If disabled, an evaluation flag is added and when the respective moz.build variables are evaluated, they see the flag and short-circuit. The module imports in testing.py were also refactored as part of this change to swallow any import failure. We had previously delay imported these modules as a way to work around the import failure in certain context. If the import fails, an exception will be thrown attempting to operate on None. This is slightly more annoying than an explicit ImportError. The reason we can't keep the import in the function is because "import" is processed at block scoping, so if an import is in a block, it gets processed, even if that line is never evaluated. Various callers not needing to access test manifest data have been changed to not load it. A side effect of this change is that various `mach file-info` commands became faster! For example, `mach file-info bugzilla-component 'testing/**'` dropped ~500ms from ~9000ms. MozReview-Commit-ID: 9mtBg4AWCc
23dbfc6d8ebf99c5c3c49656acd9ba644a6a2637: Bug 1402010 - Define evaluation flags on moz.build contexts; r?chmanchester draft
Gregory Szorc <gps@mozilla.com> - Thu, 21 Sep 2017 11:04:56 -0700 - rev 668487
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1402010 - Define evaluation flags on moz.build contexts; r?chmanchester We have different reasons for evaluating moz.build files. Today, the evaluation portion of the moz.build context/sandbox is mostly the same: the differences in behavior reside at the reader layer. This is good because we want evaluation to be as similar as possible to avoid surprises. As a subsequent commit will show, there are areas where evaluating the same way everywhere has problems and there are compelling reasons to tweak behavior under special scenarios. In this commit, we add an annotation to all moz.build context instances denoting what special evaluation modes are in effect. MozReview-Commit-ID: 2gMZ4JkJCST
51607c9defa7b2bcb537f9f7c6d9158f1357ef9f: Bug 1402010 - Don't use mutable default argument value; r?chmanchester draft
Gregory Szorc <gps@mozilla.com> - Thu, 21 Sep 2017 09:17:52 -0700 - rev 668486
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1402010 - Don't use mutable default argument value; r?chmanchester MozReview-Commit-ID: Ko2AV0KitjP
a71490730baa86f21a310b47fd975b6d36003cae: Bug 1402010 - Normalize paths according to finder's base; r?chmanchester draft
Gregory Szorc <gps@mozilla.com> - Thu, 21 Sep 2017 11:29:05 -0700 - rev 668485
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1402010 - Normalize paths according to finder's base; r?chmanchester e9416a307987f accidentally regressed various `mach file-info` commands due to the used Finder being rooted at a different directory. In this commit, we change the path normalization code to always normalize paths against the relative path to the root of the Finder being used. MozReview-Commit-ID: C3S6Zs4qPBR
83afa692da84387ded48b42f36f05911a4cbadb0: Bug 1399777 Fprinter directing output to Windows debug console when it outputs to stderr. r=Yoric
sourav3 <sourav.mukherjee619@gmail.com> - Thu, 21 Sep 2017 17:06:51 +0800 - rev 668484
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1399777 Fprinter directing output to Windows debug console when it outputs to stderr. r=Yoric MozReview-Commit-ID: 81ubXofHIlG *** Using PodCopy instead of std::copy and fixing spaces
2b87ee06ac0478e58c7a20be52b413f73ee630dc: Bug 1401997 - Always report pixel difference counts for reftests. r=jmaher
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 21 Sep 2017 11:28:24 -0400 - rev 668483
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1401997 - Always report pixel difference counts for reftests. r=jmaher MozReview-Commit-ID: 5f2JPMA1ntP
87ffa54a5436b83fb090616af2849966c64144f3: Bug 1397438 - Add subtests support for talos base vs ref pageloader tests; r=jmaher
Rob Wood <rwood@mozilla.com> - Thu, 21 Sep 2017 08:47:56 -0400 - rev 668482
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1397438 - Add subtests support for talos base vs ref pageloader tests; r=jmaher MozReview-Commit-ID: Gc4nBionzqw
d095506bd1d678c5a004ce12510707186f86963b: Bug 1396542 - Let sandboxed content processes read /var/lib/dbus/machine-id. r=gcp
Jed Davis <jld@mozilla.com> - Tue, 19 Sep 2017 19:54:41 -0600 - rev 668481
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1396542 - Let sandboxed content processes read /var/lib/dbus/machine-id. r=gcp PulseAudio is the only thing that's known to need this. Note that the same file often exists as /etc/machine-id, and we currently allow reading all of /etc (which includes other fingerprinting hazards as well). MozReview-Commit-ID: FoyKQzhAV6M
9bd41e3dcdd691e34c934e8602f96e24ad7da36e: merge mozilla-central to autoland. r=merge a=merge
Sebastian Hengst <archaeopteryx@coole-files.de> - Thu, 21 Sep 2017 17:29:34 +0200 - rev 668480
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
merge mozilla-central to autoland. r=merge a=merge
bffb6b9d72128317e400b0bc35dcde97c7068250: Bug 1401725 - Use sparse checkouts for toolchain tasks; r=glandium
Gregory Szorc <gps@mozilla.com> - Thu, 21 Sep 2017 07:30:49 -0700 - rev 668479
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1401725 - Use sparse checkouts for toolchain tasks; r=glandium Strictly speaking we don't need all files in the directories listed in the profile. But the checkout is still small enough and it is far less effort than cherry-picking every file needed by every toolchain task. This brings the checkout down to ~3700 files, which only takes 1-2s. MozReview-Commit-ID: 2BpKdZ2Pvx9
fc2264fce0d40ca7c1ac7daa1fb59e4c3f59bffa: Bug 1401710 - Remove unused unsafe code from nsDOMClassInfo. r=bz
Andrew McCreight <continuation@gmail.com> - Wed, 20 Sep 2017 13:01:48 -0700 - rev 668478
Push 81062 by gszorc@mozilla.com at Thu, 21 Sep 2017 18:37:24 +0000
Bug 1401710 - Remove unused unsafe code from nsDOMClassInfo. r=bz Also, the XPConnect() method is unused. MozReview-Commit-ID: JycZIa9TbC8
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip