5038112b5f783b726e854676d8c931fb5ec590e7: Bug 1277275 - Cache I/O queue length telemetry, r=michal
Honza Bambas <honzab.moz@firemni.cz> - Thu, 09 Jun 2016 09:00:00 +0200 - rev 301671
Push 30339 by cbook@mozilla.com at Mon, 13 Jun 2016 23:16:11 +0000
Bug 1277275 - Cache I/O queue length telemetry, r=michal
1155115a715389b86fc2608977f5bce3083d5b42: Bug 882717 - Invoke TimeMarchesOn when the startTime/endTime/pauseOnExit be changed of TextTrackCue. r=rillian
bechen <bechen@mozilla.com> - Wed, 08 Jun 2016 16:53:30 +0800 - rev 301670
Push 30339 by cbook@mozilla.com at Mon, 13 Jun 2016 23:16:11 +0000
Bug 882717 - Invoke TimeMarchesOn when the startTime/endTime/pauseOnExit be changed of TextTrackCue. r=rillian MozReview-Commit-ID: 7Xol9x83lLx
66211bb627bf801519fe8c6db5de39c0801f25ca: Bug 950401 - Add process logging to OS X / BSD. r=bsmedberg
Henrik Skupin <mail@hskupin.info> - Fri, 03 Jun 2016 18:26:15 +0200 - rev 301669
Push 30339 by cbook@mozilla.com at Mon, 13 Jun 2016 23:16:11 +0000
Bug 950401 - Add process logging to OS X / BSD. r=bsmedberg MozReview-Commit-ID: bEPQabbSP1
ea5833a015a141c08d9d63b768841af97287033f: Bug 877856 - Remove obsolete defaultset attributes from default toolbars, r=gijs
Akshat Kedia <akshat.kedia@outlook.com> - Sat, 11 Jun 2016 17:53:35 +0530 - rev 301668
Push 30338 by cbook@mozilla.com at Mon, 13 Jun 2016 23:12:41 +0000
Bug 877856 - Remove obsolete defaultset attributes from default toolbars, r=gijs MozReview-Commit-ID: Ve8PWDg96
405bdbc110e121282d453fcf66cbf0daa8c3441e: Bug 1277967 - Use defaultFavicon for default search image. r=florian
Michael Kaply <mozilla@kaply.com> - Mon, 13 Jun 2016 09:36:29 +0100 - rev 301667
Push 30338 by cbook@mozilla.com at Mon, 13 Jun 2016 23:12:41 +0000
Bug 1277967 - Use defaultFavicon for default search image. r=florian
fbc8f897e016fe44393bb2e3c064071598b8f586: Backed out changeset c7ddd550008c (bug 1171736) for breaking gecko-decision opt. r=backout on a CLOSED TREE
Sebastian Hengst <archaeopteryx@coole-files.de> - Sun, 12 Jun 2016 21:01:43 +0200 - rev 301666
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Backed out changeset c7ddd550008c (bug 1171736) for breaking gecko-decision opt. r=backout on a CLOSED TREE
c7ddd550008cd59ccb7629247d9296b95cdb9925: Bug 1171736 - Add taskcluster scheduling logic (on try) for linux l10n. r=sfink
Justin Wood <Callek@gmail.com> - Mon, 06 Jun 2016 16:09:51 -0400 - rev 301665
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1171736 - Add taskcluster scheduling logic (on try) for linux l10n. r=sfink MozReview-Commit-ID: Auz7sOW5Ptr
d1722ce2542a2dcc6d351da7481640aceb44f894: Bug 1279633 - Define AsmJSCache_MIN in terms of AsmJSCacheSuccess, instead of the other way around; r=till
Nick Fitzgerald <fitzgen@gmail.com> - Sun, 12 Jun 2016 08:04:48 -0700 - rev 301664
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1279633 - Define AsmJSCache_MIN in terms of AsmJSCacheSuccess, instead of the other way around; r=till rust-bindgen will make an enum variant for the first definition it encounters, and then define duplicates as constants outside of the enum definition. This has the unfortunate effect of making AsmJSCache_MIN an enum variant and AsmJSCache_Success the constant definition outside of the enum in the case of the AsmJSCacheResult enumeration. This commit rectifies that. This upstreams the following commit from servo/mozjs: 50f47cf Bind AsmJSCache_Success rather than AsmJSCache_MIN
4073f541e59556b7f9a8e0d7078165dd74050863: Bug 1279349 - Untabify js/src/make-source-package.sh; r=sfink
Nick Fitzgerald <fitzgen@gmail.com> - Sun, 12 Jun 2016 08:01:26 -0700 - rev 301663
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1279349 - Untabify js/src/make-source-package.sh; r=sfink
8782b81c1b05f46e140e4eabe1c6f559715291ac: Bug 1275638 - Move libmozjs to the upload directory; r=sfink
Nick Fitzgerald <fitzgen@gmail.com> - Sun, 12 Jun 2016 08:01:26 -0700 - rev 301662
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1275638 - Move libmozjs to the upload directory; r=sfink
559f31d84a6e05ffcc1231f114cdc26c39afa72c: Bug 1279453 - Remove separate worker binding for ServiceWorkerRegistration API, r=bkelly
Andrea Marchesini <amarchesini@mozilla.com> - Sun, 12 Jun 2016 16:26:51 +0200 - rev 301661
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1279453 - Remove separate worker binding for ServiceWorkerRegistration API, r=bkelly
6a6aa8a42eb1f71c70bf0bbab7cf3e38e8bb9c90: Bug 1276880 - 'Open link in a new <container_name> Tab' in the context menu, r=gijs
Andrea Marchesini <amarchesini@mozilla.com> - Sun, 12 Jun 2016 16:23:10 +0200 - rev 301660
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1276880 - 'Open link in a new <container_name> Tab' in the context menu, r=gijs
5834abf0aebb53d59c2ab4bea68448bd62a03d74: Bug 1279108 - Disable leak detection for updater xpcshell tests. r=mccr8
Mike Hommey <mh+mozilla@glandium.org> - Fri, 10 Jun 2016 12:08:44 +0900 - rev 301659
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1279108 - Disable leak detection for updater xpcshell tests. r=mccr8 With more recent version of ASAN, the updater program shows multiple leaks, for different reasons. One is that the updater code heavily relies on pointers into a large buffer, with exceptions, making things difficult to avoid leaks of those exceptions. At least it requires more effort than I'm willing to put for the sake of upgrading the compiler we use for ASAN. Another is that the leak suppressions are not currently used for xpcshell tests, and some leaks attributed to libglib, that would normally be suppressed, are not. Moreover, even if the suppressions were used, it looks like some are not rooted to already suppressed system libraries, and would require investigation. Ideally, we'd have debug symbols installed for the system libraries and would have full stack traces, but we don't, so this makes the whole process harder than necessary. All in all, the updater is a separate short-lived program, and until we can address all the problems above, we can just ignore memory leaks in it (which aren't new anyways and are ignored by not being detected by the ASAN currently used on automation). We don't disable ASAN entirely, though, only leak detection, and only for the updater program.
6803c5e3f34b6e9f9f39366d3c1c770f99fb0af9: Bug 1278456 - Remove stdc++-compat hacks for libstdc++ < 4.6.1. r=froydnj
Mike Hommey <mh+mozilla@glandium.org> - Tue, 07 Jun 2016 13:52:04 +0900 - rev 301658
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1278456 - Remove stdc++-compat hacks for libstdc++ < 4.6.1. r=froydnj
93a4f9e7a6b0f9c447d2dd68ab6782c0360085b1: Bug 1278456 - Add the tooltool GCC library directory to LD_LIBRARY_PATH on Linux builds. r=mshal
Mike Hommey <mh+mozilla@glandium.org> - Tue, 07 Jun 2016 13:50:36 +0900 - rev 301657
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1278456 - Add the tooltool GCC library directory to LD_LIBRARY_PATH on Linux builds. r=mshal Build slaves on automation are based on Centos 6, which doesn't have a recent enough version of libstdc++ for our new requirements. But since we're building with a recent GCC or clang with its own libstdc++, we do have such a libstdc++ available somewhere, and the compiler picks it when invoking the linker. Problems start happening when we execute some of the built programs during the build, like host tools (e.g. nsinstall), or target programs (xpcshell, during packaging). In that case, we need the compiler's libstdc++ to be used. Which required adding the GCC or clang library directory to LD_LIBRARY_PATH. Unconveniently enough, the clang 3.5 tooltool package we're using for ASAN builds until we can update to at least 3.8 (bug 1278718) doesn't contain libstdc++.so. So for those builds, pull the GCC package from tooltool as well, and pick libstdc++ from there.
42c217cffdf87f4e4c6bd8f0a386b950823d9678: Bug 1278456 - Bump libstdc++ requirement to 3.4.16 (4.6.1). r=froydnj
Mike Hommey <mh+mozilla@glandium.org> - Tue, 07 Jun 2016 13:51:05 +0900 - rev 301656
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1278456 - Bump libstdc++ requirement to 3.4.16 (4.6.1). r=froydnj Similarly to the considerations about glibc, the Linux compatibility matrix (https://developer.mozilla.org/en-US/Firefox/Linux_compatibility_matrix) tells us no distro with Gtk+3 3.4 has a version of libstdc++ older than 4.6. The data in the matrix doesn't go to that level of detail, but Ubuntu 12.04 LTS, being the only one with version 4.6 (others have at least 4.7), it's worth noting it has version 4.6.3. Which means we can safely require libstdc++ symbols version 3.4.16 (which were added in 4.6.1). This will allow us to remove a lot of the stdc++ compatibility hacks.
92c44ebd3d6eea3154d72738421d58b62d2dbe07: Bug 1278456 - Bump glibc requirement to 2.12. r=froydnj
Mike Hommey <mh+mozilla@glandium.org> - Tue, 07 Jun 2016 13:49:47 +0900 - rev 301655
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1278456 - Bump glibc requirement to 2.12. r=froydnj The requirement for glibc has been set to version 2.7 for a long while. Spidermonkey uses the pthread_setname_np symbol, which is only available since glibc 2.12. So far, we've been fortunate that the symbol doesn't end up in libxul, or tests that link to js directly, because the symbol is eliminated as being called by effectively dead code. There are multiple reasons why this is going to change, one of which being changes to the way things are linked, that will make the linker not eliminate that code in some cases. Another is that eventually, the separation of build systems between js and top-level is going to fade, and the glibc checks, which apply to all gecko binaries, will also apply to js binaries. They currently are not happening, and would fail because of pthread_setname_np if they were. Taking a step back, as of version 46, the mozilla.org builds require at least Gtk+3 3.4. Which means the requirements for the underlying system have received a dramatic bump, and it's time to revisit the requirements for binary compatibility. I went through all my notes from all the recent times binary compatibility has been considered, and put together a compatibility matrix on MDN from that data as well as more recent data that I could find here and there, about the major non-rolling-release distros (RHEL, Fedora, SuSE, Debian, Ubuntu) https://developer.mozilla.org/en-US/Firefox/Linux_compatibility_matrix Considering the data there, none of the distros that have at least Gtk+3 3.4 have a glibc older than 2.13. The list of symbols that 2.13 provides that 2.12 doesn't have is not large enough, though, to really care about depending on 2.13.
6f78f70eb2ee57fb0b65b99ebc9a5a55ffd88f9f: Merge mozilla-central to mozilla-inbound
Carsten "Tomcat" Book <cbook@mozilla.com> - Sun, 12 Jun 2016 11:31:50 +0200 - rev 301654
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Merge mozilla-central to mozilla-inbound
84f7d596ce226bacc2ab52ba064b071b0d8df864: Bug 1254898 - Part 3. Focus browser when test start for fullscreen mode. r=avih
Ethan Lin <ethlin@mozilla.com> - Sun, 29 May 2016 19:46:00 +0200 - rev 301653
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1254898 - Part 3. Focus browser when test start for fullscreen mode. r=avih
54d7a042b8b76cdaf8b9ec4827e8952745c509f6: Bug 1254898 - Part 2. Add video clips for talos video test. r=avih,jmaher
Ethan Lin <ethlin@mozilla.com> - Mon, 09 May 2016 08:17:00 +0200 - rev 301652
Push 30337 by cbook@mozilla.com at Mon, 13 Jun 2016 08:05:05 +0000
Bug 1254898 - Part 2. Add video clips for talos video test. r=avih,jmaher
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip