f7624079d0b218eeb26199330f8363d86d00fb13: Bug 1423102 - cache l10n values in RequestListColumnTransferredSize;r=Honza
Fred Lin <gasolin@gmail.com> - Fri, 01 Dec 2017 10:08:43 +0800 - rev 707655
Push 92188 by kgupta@mozilla.com at Tue, 05 Dec 2017 16:54:08 +0000
Bug 1423102 - cache l10n values in RequestListColumnTransferredSize;r=Honza MozReview-Commit-ID: 6wqz7x7Xos7
45c202561c1e52cf7550a41f2e335f1a10e8ffd2: Bug 1423107 - Remove moz_posix_memalign. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 05 Dec 2017 16:52:34 +0900 - rev 707654
Push 92188 by kgupta@mozilla.com at Tue, 05 Dec 2017 16:54:08 +0000
Bug 1423107 - Remove moz_posix_memalign. r=njn
d9adbaf945bba0d7b5286e94f1ce2354aaff587c: Bug 1423107 - Replace uses of moz_posix_memalign with posix_memalign. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 05 Dec 2017 16:46:17 +0900 - rev 707653
Push 92188 by kgupta@mozilla.com at Tue, 05 Dec 2017 16:54:08 +0000
Bug 1423107 - Replace uses of moz_posix_memalign with posix_memalign. r=njn moz_posix_memalign is a wrapper for posix_memalign that only exists if posix_memalign exists. On OSX, it has a fallback for an under-specified bug where it purportedly returns a pointer that doesn't have the requested alignment. That fallback was added in bug 414946, over 6 years ago, before jemalloc was even enabled on OSX. Considering posix_memalign is used directly in many other places in Gecko, that we almost always use mozjemalloc, which doesn't have these problems, and that in all likeliness, the bug was in some old version of OSX that is not supported anymore, the fallback does not seem all that useful. So, just use posix_memalign directly.
3e1e665e2a36d1323a24abd85f57dd6c2f08694f: servo: Merge #19473 - geckolib: Fix typo in CSS parser error message name (from servo:error-message); r=aethanyc
Cameron McCormack <cam@mcc.id.au> - Tue, 05 Dec 2017 00:54:12 -0600 - rev 707652
Push 92188 by kgupta@mozilla.com at Tue, 05 Dec 2017 16:54:08 +0000
servo: Merge #19473 - geckolib: Fix typo in CSS parser error message name (from servo:error-message); r=aethanyc Source-Repo: https://github.com/servo/servo Source-Revision: 005fd9cfa864a22473d0cdb980a11b874bcd1b03
33e35ba1c14ba5bfe1f55f58f5c67706fe839a40: Bug 1417051 - Reorganize Firefox UI tests in test package for full path names in log files. r=maja_zf
Henrik Skupin <mail@hskupin.info> - Fri, 01 Dec 2017 10:27:06 +0100 - rev 707651
Push 92188 by kgupta@mozilla.com at Tue, 05 Dec 2017 16:54:08 +0000
Bug 1417051 - Reorganize Firefox UI tests in test package for full path names in log files. r=maja_zf The Firefox UI tests were packaged wrongly, and as such didn't use the real path as in tree. This patch fixes that by separating the packaging logic for the harness, and the tests. Also it updates the mozharness script to run the Firefox UI tests command by using the test folder as current working directory. This will make sure that the relative path to the tests is reported. It's identical to the location in the tree. MozReview-Commit-ID: 3YVfCw4RWfV
eadb73ce9eb7c692eb1b4e8e5ecc99825d226639: Bug 1417051 - Mozharness has to run Marionette tests from tests folder. r=maja_zf
Henrik Skupin <mail@hskupin.info> - Thu, 30 Nov 2017 17:55:03 +0100 - rev 707650
Push 92188 by kgupta@mozilla.com at Tue, 05 Dec 2017 16:54:08 +0000
Bug 1417051 - Mozharness has to run Marionette tests from tests folder. r=maja_zf Updates the mozharness script to run the Marionette command by using the test folder as current working directory. This will make sure that the relative path to the tests is reported. It's identical to the location in the tree. MozReview-Commit-ID: 6hOQnJSqfv0
e7662cc12ccbc28a9a0c9fec551249a660e7cc18: Bug 1417051 - Report relative path to Marionette test modules starting from cwd. r=maja_zf
Henrik Skupin <mail@hskupin.info> - Thu, 30 Nov 2017 17:03:18 +0100 - rev 707649
Push 92188 by kgupta@mozilla.com at Tue, 05 Dec 2017 16:54:08 +0000
Bug 1417051 - Report relative path to Marionette test modules starting from cwd. r=maja_zf Only reporting the basename of the test module doesn't allow someone to easily figure out where the file is actually located. Instead the current working directory should be used, and the test module path reported as relative path. MozReview-Commit-ID: 8FdYNw4ocjL
ba56ac3d6603a2cb096785553578c929f31074df: Bug 1417051 - Don't report test start/end twice. r=maja_zf
Henrik Skupin <mail@hskupin.info> - Thu, 30 Nov 2017 16:08:10 +0100 - rev 707648
Push 92188 by kgupta@mozilla.com at Tue, 05 Dec 2017 16:54:08 +0000
Bug 1417051 - Don't report test start/end twice. r=maja_zf The harness already logs the start and end of the test via mozlog. So there is no need to do it twice. Especially because this requires another command send to Marionette server. MozReview-Commit-ID: 5JfU9XgbVqx
9e690062e7b70114f2596733679103f094c68888: Bug 1421968 - Enable ESLint rule mozilla/use-services by default, but whitelist it for various directories still to be fixed. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Tue, 28 Nov 2017 19:24:12 +0000 - rev 707647
Push 92187 by bmo:standard8@mozilla.com at Tue, 05 Dec 2017 16:50:05 +0000
Bug 1421968 - Enable ESLint rule mozilla/use-services by default, but whitelist it for various directories still to be fixed. r?Mossop MozReview-Commit-ID: KOZWr7FiDQZ
fdf2c537900e3b123feb788111fa92bac9c21d0d: Bug 1421968 - Fix more instances of .getService to use Services.jsm where possible. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Thu, 30 Nov 2017 12:04:16 +0000 - rev 707646
Push 92187 by bmo:standard8@mozilla.com at Tue, 05 Dec 2017 16:50:05 +0000
Bug 1421968 - Fix more instances of .getService to use Services.jsm where possible. r?Mossop MozReview-Commit-ID: 2EbsWq7VPrI
d31156c3cf7467a42560e195910043eeecb0bbbd: Bug 1417678 - New search defaults for browser and mobile. r?florian draft
Michael Kaply <mozilla@kaply.com> - Fri, 01 Dec 2017 11:43:54 -0600 - rev 707645
Push 92186 by mozilla@kaply.com at Tue, 05 Dec 2017 16:49:48 +0000
Bug 1417678 - New search defaults for browser and mobile. r?florian MozReview-Commit-ID: FP9f7QbXZAV
1a8a5a358e4107fa6d6e76fb20533baccf2b4737: Bug 1241131 - Remove DevTools reload addon histograms;r=francois draft
Julian Descottes <jdescottes@mozilla.com> - Thu, 30 Nov 2017 19:09:24 +0100 - rev 707644
Push 92185 by jdescottes@mozilla.com at Tue, 05 Dec 2017 16:42:36 +0000
Bug 1241131 - Remove DevTools reload addon histograms;r=francois MozReview-Commit-ID: oq7SVGPI2t
c756fdc612dca8e86dae422f64003fda2c6e985d: Bug 1241131 - Remove DevTools reload addon;r=ochameau draft
Julian Descottes <jdescottes@mozilla.com> - Thu, 30 Nov 2017 19:08:44 +0100 - rev 707643
Push 92185 by jdescottes@mozilla.com at Tue, 05 Dec 2017 16:42:36 +0000
Bug 1241131 - Remove DevTools reload addon;r=ochameau In the end I prefer to remove the addon completely, if we need it for go faster we can simply reintroduce it. MozReview-Commit-ID: GCS4ZRvwUcs
6de3d503a014da6c5c297d3733be222b42d9710f: Bug 1423010 - 3. Clean up o.m.g.gfx package; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Tue, 05 Dec 2017 11:40:10 -0500 - rev 707642
Push 92184 by bmo:nchen@mozilla.com at Tue, 05 Dec 2017 16:40:26 +0000
Bug 1423010 - 3. Clean up o.m.g.gfx package; r?rbarker Remove unused classes and make classes that are not used outside of the package package-private. MozReview-Commit-ID: 9FxcL5QsM1Q
c088555cddd84d8bac006379db0b555aa2cabf56: Bug 1423010 - 2. Fix other code that use BitmapUtils; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Tue, 05 Dec 2017 11:40:10 -0500 - rev 707641
Push 92184 by bmo:nchen@mozilla.com at Tue, 05 Dec 2017 16:40:26 +0000
Bug 1423010 - 2. Fix other code that use BitmapUtils; r?rbarker Use o.m.g.util.BitmapUtils in code that use BitmapUtils. MozReview-Commit-ID: KPM05Aqf1kW
1f344d891a2a92d694a443db03665a027b04bca5: Bug 1423010 - 1. Move BitmapUtils to util package; r?rbarker draft
Jim Chen <nchen@mozilla.com> - Tue, 05 Dec 2017 11:40:10 -0500 - rev 707640
Push 92184 by bmo:nchen@mozilla.com at Tue, 05 Dec 2017 16:40:26 +0000
Bug 1423010 - 1. Move BitmapUtils to util package; r?rbarker I think BitmapUtils is better suited for the o.m.g.util package instead of o.m.g.gfx, since none of the other classes in gfx actually use BitmapUtils. MozReview-Commit-ID: IEwSIb5h9Y7
e650283c9bb3ee174b58f8591a785663677cde8f: Bug 1319222 - Enable compilation on all directories in the tup backend; r=chmanchester draft
Mike Shal <mshal@mozilla.com> - Wed, 22 Nov 2017 13:26:33 -0500 - rev 707639
Push 92183 by bmo:mshal@mozilla.com at Tue, 05 Dec 2017 16:33:02 +0000
Bug 1319222 - Enable compilation on all directories in the tup backend; r=chmanchester MozReview-Commit-ID: D5NlgEHVydZ
402cf6be86dd6723930c7a0b93bbd0341f5f53c0: Bug 1319222 - Support compiling *.s with yasm; r=chmanchester draft
Mike Shal <mshal@mozilla.com> - Wed, 22 Nov 2017 17:12:50 -0500 - rev 707638
Push 92183 by bmo:mshal@mozilla.com at Tue, 05 Dec 2017 16:33:02 +0000
Bug 1319222 - Support compiling *.s with yasm; r=chmanchester The moz.build files that specify USE_YASM = True will get the value of AS_DASH_C_FLAG and AS overwritten in PassthruVariables. We can save those in the BackendTupfile and use them in place of the configure or default settings as appropriate. This enables compilation of those .s files that are built with yasm. MozReview-Commit-ID: J66q8nKQ0an
2972a5a54694c82661cbcafa7bc920f3023c8247: Bug 1319222 - Enable host compilation in the tup backend; r=chmanchester draft
Mike Shal <mshal@mozilla.com> - Wed, 22 Nov 2017 16:24:33 -0500 - rev 707637
Push 92183 by bmo:mshal@mozilla.com at Tue, 05 Dec 2017 16:33:02 +0000
Bug 1319222 - Enable host compilation in the tup backend; r=chmanchester MozReview-Commit-ID: 4hp6oH7YOd7
4e51e717bd72dfc992f8f51777a8f6aca344dc43: Bug 1319222 - Add include flags to HOST_*; r?chmanchester draft
Mike Shal <mshal@mozilla.com> - Wed, 22 Nov 2017 16:23:44 -0500 - rev 707636
Push 92183 by bmo:mshal@mozilla.com at Tue, 05 Dec 2017 16:33:02 +0000
Bug 1319222 - Add include flags to HOST_*; r?chmanchester This accounts for LOCAL_INCLUDES in the moz.build files, as well as the default INCLUDES specified in config.mk that are used for host compilation. Since some of the HOST_CFLAGS were also used for linking, those flags are split off into HOST_C{XX}_LDFLAGS so that the linker-only flags can be placed in those variables. MozReview-Commit-ID: J1LxIZVeFJ
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip