fa40c16f194c89b4db36c1495a33f0a62c32dfb0: Bug 1433144 - Update web-platform-tests to revision 2e19bfdaee6edb2c1069c07e14037284167284a3, a=testonly
James Graham <james@hoppipolla.co.uk> - Tue, 23 Jan 2018 16:14:20 +0000 - rev 749096
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1433144 - Update web-platform-tests to revision 2e19bfdaee6edb2c1069c07e14037284167284a3, a=testonly MozReview-Commit-ID: 13sFeYHTYGC
031ccad355e47f0697deeedd956753dc8fcb48b4: Bug 1433139 - Follow-up to adjust keybindings to work on Windows. r=mikedeboer
Dzmitry Malyshau <kvark@mozilla.com> - Tue, 30 Jan 2018 12:28:52 -0500 - rev 749095
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1433139 - Follow-up to adjust keybindings to work on Windows. r=mikedeboer MozReview-Commit-ID: 8AmnZzDKu8p
dc0e8ad85292559a7099016daa4ec25a0f70f630: Backed out changeset 62da02a0aa77 (bug 1433005) for Gtest failures on Linux x64 asan and Windows 10 x64 debug
Gurzau Raul <rgurzau@mozilla.com> - Tue, 30 Jan 2018 19:14:12 +0200 - rev 749094
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Backed out changeset 62da02a0aa77 (bug 1433005) for Gtest failures on Linux x64 asan and Windows 10 x64 debug
bbeba6852662baf66697e097522b9ba2fc8eccd6: Bug 1351197 - Re-enable TelemetryModules test on Android on Release and Beta. r=gfritzsche
Marco Castelluccio <mcastelluccio@mozilla.com> - Mon, 29 Jan 2018 12:09:14 +0100 - rev 749093
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1351197 - Re-enable TelemetryModules test on Android on Release and Beta. r=gfritzsche
5fc179e245d51289f1f7bcaba0c29189d3336fbf: Bug 1421380 - Enable gfx.webrender.hit-test by default. r=jrmuizel
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 29 Jan 2018 16:35:10 -0500 - rev 749092
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1421380 - Enable gfx.webrender.hit-test by default. r=jrmuizel This causes some mochitests to fail. MozReview-Commit-ID: J2AjM0qKVE5
c182e492a2e7f1477851bcd5bca8e97ef235a3d7: Bug 1421380 - Don't do a composite of WR rendered frames unless a composite is requested. r=nical
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 29 Jan 2018 16:35:10 -0500 - rev 749091
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1421380 - Don't do a composite of WR rendered frames unless a composite is requested. r=nical We sometimes render frames for hit-testing consistency requirements but those frames don't need compositing. This goes with webrender PR 2358. MozReview-Commit-ID: D6DRF040D5a
ca489678fdedaff1c660dddf7ee62c966787b59a: servo: Merge #19908 - Double the sccache timeout (from servo:jdm-patch-9); r=emilio
Josh Matthews <josh@joshmatthews.net> - Tue, 30 Jan 2018 10:59:18 -0600 - rev 749090
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
servo: Merge #19908 - Double the sccache timeout (from servo:jdm-patch-9); r=emilio Fixes #19907. Source-Repo: https://github.com/servo/servo Source-Revision: 86b7af5db55ac340517318c0305dacf00208dd96
f622490e845dbc236480ca7acb5e821eb97fefdf: Bug 1429129 - Add enterprise policy to remove "Set As Desktop Background" context menu option r=Felipe,Gijs
Kirk Steuber <ksteuber@mozilla.com> - Mon, 29 Jan 2018 13:24:26 -0800 - rev 749089
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1429129 - Add enterprise policy to remove "Set As Desktop Background" context menu option r=Felipe,Gijs MozReview-Commit-ID: EdVKcujYUh4
5c7b21fa7315ca753684881b3dc3cee5ec235ca7: Bug 1420975 - Add a environment variable to record JS stack for leaks. r=froydnj,mrbkap
Andrew McCreight <continuation@gmail.com> - Wed, 10 Jan 2018 14:02:45 -0800 - rev 749088
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1420975 - Add a environment variable to record JS stack for leaks. r=froydnj,mrbkap This patch adds a new environment variable XPCOM_MEM_LOG_JS_STACK that changes XPCOM leakchecking to record a JS stack for all objects, in addition to a C++ stack. This is useful when a C++ object is being leaked due to JS. The JS stack will be printed if the object leaks, if it is used in combination with XPCOM_MEM_BLOAT_LOG=1 and XPCOM_MEM_LOG_CLASSES=nsFoo, if nsFoo is the class of interest. This patch moves a few XPConnect functions for recording the stack into xpcpublic.h so they can be called from nsTraceRefcnt.cpp. MozReview-Commit-ID: FX2QVCSXz4f
e16fc8abd345b6b4afb9c3e5541e7e684894b7c0: Bug 1368699 - Post: Remove PURGECACHES from Make and now-unused app-rules.mk. r=gps
Nick Alexander <nalexander@mozilla.com> - Fri, 19 Jan 2018 10:50:42 -0800 - rev 749087
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1368699 - Post: Remove PURGECACHES from Make and now-unused app-rules.mk. r=gps Now that writing the .purgecaches sentinel is done by |mach build|, we can remove it from Make. In addition, we can cull the now-unused app-rules.mk \o/ MozReview-Commit-ID: 6CnAqLeZwzB
35a5db01b6ae991b2c1f538d012b43085dc3533d: Bug 1368699 - Write .purgecaches sentinels every |mach build|. r=gps
Nick Alexander <nalexander@mozilla.com> - Tue, 23 Jan 2018 19:18:16 -0800 - rev 749086
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1368699 - Write .purgecaches sentinels every |mach build|. r=gps This adds a new `post_build` step to each `BuildBackend` implementation, and uses it to write .purgecaches after every |mach build| invocation -- including after |mach build TARGET| invocations. This approach should be more robust than the existing recursive-Make based solution, which seems to not write the .purgecaches files in some situations. In addition, the recursive-Make solution does not generalize to other backends, in particular Tup. It is possible that the Tup backend will handle writing the .purgecaches sentinel as part of its regular build process, but discussions with mshal suggest that there's no convenient way for Tup to write .purgecaches only when something *changes* during the build. That is, Tup can achieve the behaviour implemented by this patch, but it's not easier to do better by not writing .purgecaches when the caches do not in fact need to be purged. I elected to bake in the special knowledge of --enable-application=browser and macOS here since this whole process is special. If we need to generalize, we could add a moz.configure option specifying the purgecaches directories, but it doesn't seem worth it right now. The ideal approach would be to determine FINAL_TARGET from the application directory, but that is determined by DIST_SUBDIR. In addition, it's not clear how to present that information to the post-build step in a build-backend agnostic manner. This will require tweaking as we migrate the macOS bundle handling to moz.build, especially in browser/app. See https://bugzilla.mozilla.org/show_bug.cgi?id=1223748, which could improve this significantly. MozReview-Commit-ID: 63KZy18D23i
7297a1e8c4ff85c1c9d64abbacc11d59f99bee3e: Bug 1368699 - Pre: Remove MY_{CONFIG,RULES} Makefile customization hooks. r=gps
Nick Alexander <nalexander@mozilla.com> - Fri, 19 Jan 2018 10:43:51 -0800 - rev 749085
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1368699 - Pre: Remove MY_{CONFIG,RULES} Makefile customization hooks. r=gps I very much doubt these are used, but even if we are -- we shouldn't support this type of local customization, since it doesn't extend to non-Make-based backends. With the customization point removed, there's no way to set ETAGS, so we remove what little support there was for generating Emacs tags. MozReview-Commit-ID: IEF2Q4tISEn
53fa60c5e8b41f30e410f8cb5e7611fb08c8fc6f: Bug 1433285: Extract classes*.dex from .ap_ --with-gradle. r=gps,snorp
Nick Alexander <nalexander@mozilla.com> - Wed, 24 Jan 2018 22:09:48 -0800 - rev 749084
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1433285: Extract classes*.dex from .ap_ --with-gradle. r=gps,snorp Right now, we only expect classes.dex, and even --with-gradle we copy it out of $topobjdir/mobile/android/base. This commit changes that for --with-gradle: we only take classes.dex from the given .ap_ file, and we also handle multiple classesN.dex files (for future multi-dex support). The moz.build system stays the same. This avoids an issue with newer Android-Gradle plugins, where the classes.dex produced could be either in dex/ or in dexMerger/, depending on whether any external libraries needed merging. By extracting classes.dex from the .ap_ file, we don't need to know what Gradle build steps actually occur. The classes.dex in the package-manifest.in has been irrelevant since Bug 1260241. MozReview-Commit-ID: FozKwjTcMzU
2afca7ece7b741ef5a1ef51c355d3ef44b943469: Bug 1425340 - Remove unused DisplayItemScrollClip files. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Thu, 14 Dec 2017 15:59:35 -0600 - rev 749083
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1425340 - Remove unused DisplayItemScrollClip files. r=mattwoodrow MozReview-Commit-ID: 2GLI4KVoBiI
17a0e7ddfb483356fb7caaee66fb2170b7d45dfe: Bug 1102240 - rename actors/inspector/inspector.js to inspector-actor.js;r=pbro
Julian Descottes <jdescottes@mozilla.com> - Fri, 26 Jan 2018 13:15:06 +0100 - rev 749082
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1102240 - rename actors/inspector/inspector.js to inspector-actor.js;r=pbro MozReview-Commit-ID: dfzTyhZXez
8e3c63c83301f63943e08a4a4284ee28bb1b1ee9: Bug 1102240 - split inspector actor in smaller files;r=ochameau,pbro
Julian Descottes <jdescottes@mozilla.com> - Fri, 26 Jan 2018 13:11:58 +0100 - rev 749081
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1102240 - split inspector actor in smaller files;r=ochameau,pbro MozReview-Commit-ID: LgZav4dMQRR
4c42b9b8bd98c6f378f94a6fc896d4a58964ec67: Bug 1102240 - Move inspector actor to dedicated folder;r=pbro
Julian Descottes <jdescottes@mozilla.com> - Fri, 26 Jan 2018 11:49:48 +0100 - rev 749080
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1102240 - Move inspector actor to dedicated folder;r=pbro MozReview-Commit-ID: LNgHweYJXcB
6639a46610c1f408fc5abebb91f490222dcdca1f: Bug 1434326: Cleanup DiagnosticsMatcher constructor. r=mystor
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 30 Jan 2018 17:40:00 +0100 - rev 749079
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1434326: Cleanup DiagnosticsMatcher constructor. r=mystor Removing a bit of the ugly :) MozReview-Commit-ID: ATf2b2oh1F1
31a0af4e29bbf601613a99d85ac4426d0a3251e8: Bug 1429815 - Fix InstallManifest::add_entries_from with non-trivial base. r=gps
Nick Alexander <nalexander@mozilla.com> - Thu, 18 Jan 2018 16:58:07 -0800 - rev 749078
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1429815 - Fix InstallManifest::add_entries_from with non-trivial base. r=gps There's a bug in InstallManifest::add_entries_from: some of the manifest entries bake their destination into both the manifest key and the manifest value, and add_entries_from with a non-empty "base" parameter to prepend to the destination only updates the manifest key and not the value. This bug causes |mach watch| to fail to _read_ the unified manifest that aggregates all of the build manifests relevant to |mach watch| that |mach build-backend -b FasterMake| successfully _wrote_, because the manifest keys are validated against the manifest values written to disk. I see no way to address this other than to manually reach into the manifest values and patch the internal destination parameter, which this patch does. MozReview-Commit-ID: FVyRB41NnHa
ec90dfc1563680727d1b377e823db48a7ff5aa1f: Bug 1413314 - Change precise increment to Ctrl instead of Alt for Linux compat; r=jryans
abhinav <abhinav.koppula@gmail.com> - Fri, 26 Jan 2018 23:36:21 +0530 - rev 749077
Push 97316 by bmo:continuation@gmail.com at Tue, 30 Jan 2018 22:53:01 +0000
Bug 1413314 - Change precise increment to Ctrl instead of Alt for Linux compat; r=jryans MozReview-Commit-ID: ErTw1XnmWV5
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip