I realized of this when @bzbarsky mentioned the bloom filter in https://bugzilla.mozilla.org/show_bug.cgi?id=1348935#c7.
Right now we hash (the hash) all the time, when we can do better.
This requires a change in string-cache, which is at https://github.com/servo/string-cache/pull/183.
Source-Repo: https://github.com/servo/servo
Source-Revision: a811776df478a009ac6a7785ad13684e3a8e0925
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : a84fb1b7a5ccab19ecfa8bb57499719f881fd1c1
For touching servo/. (This is Autoland's fault for landing it.)
--HG--
extra : amend_source : a31555ab2a959af8e57f78f4f8b1d5e9700c0fb7
extra : histedit_source : 73e44d941d04553b9766ca75d3ad33618fe4f3f5%2C8f568b83aec10dc07a1e9c6cf2b32797cb9236e3
There's quite a few changes in here. At a high level, all we're trying to do
is to replace the old update popup with a less intrusive and more modern
doorhanger (set of doorhangers) for various update failure conditions.
MozReview-Commit-ID: 24sESMTosNX
--HG--
extra : rebase_source : ee0c1e00fe3f99e16388f0de17274ff97a3b9fcf
It isn't needed until we create a context menu.
MozReview-Commit-ID: 4kCfq9PzVPV
--HG--
extra : rebase_source : 51907d6aa28d5bd2a9fb8a0acb28cac719888292
This avoids importing ContentWebRTC.jsm unless webrtc is actually
being used, which reduces memory usage.
MozReview-Commit-ID: GlMo1WIZEFD
--HG--
extra : rebase_source : 25476c825bef1948f22d0e6dae67dc01ab41f886
This avoids importing ContentWebRTC.jsm just to register observers
that may never observe anything. Avoiding importing .jsms reduces
memory usage.
ContentObserver.js gets loaded once per content process, so I think
the ._initialized stuff is not needed in the process script.
MozReview-Commit-ID: 5r9L3bfFS0U
--HG--
extra : rebase_source : 0fe6e14c2963efccf21bd1606885098902fed598
Without the use of an upstream the first repo cloned on a machine will
be cached. If a subsequent job references a different repo, it may have
to pull thousands of changesets because those changesets aren't part of
the initially-cloned repo. This is why the --upstream feature to
robustclone exists and is why it uses the mozilla-unified repo.
The mozilla-unified repo is a superset of central, aurora, beta, release,
etc. So by cloning it, you get changesets for all of the repos at the
time of the clone. When a subsequent job comes along and requests
a changeset from a different repo, you likely only need to fetch data
for a handful of changesets, not thousands.
This change adds the upstream url config for all fx_desktop_build jobs,
ensuring it is used. A redundant config entry for the try repo has been
removed as well.
MozReview-Commit-ID: 3EL7aSXS4AG
--HG--
extra : rebase_source : 19fc7373da56ad879b4b813a379dd8d9798909e4
I think I initially defined these and I think I know why I used
mozilla-central (it had to do with try not advertising bundles and
mozilla-unified being generaldelta when other repos were not). Those
reasons are no longer valid and we should be using mozilla-unified
everywhere.
MozReview-Commit-ID: CFaZspU6A5M
--HG--
extra : rebase_source : 79b74038307a3faa9b150a7ea1d449cad472e748
The webrtc gyp files have a 'build_for_tool' flag that controls among other
things what defines are provided at build time. This meant that during a
firefox valgrind build webrtc would still specify NVALGRIND, thus disabling
some valgrind macros. Similarly there are flags for asan and tsan that we
should probably have been specifying as well. This patch sets the
'build_for_tool' flag to the appropriate value when building under valgrind,
asan, and tsan.
Dão Gottwald
Henri Sivonen
nechen
Servo VCS Sync
Emilio Cobos Álvarez
Gregory Szorc
Brad Werth
Sebastian Hengst
Doug Thayer
Blake Kaplan
Kearwood Gilbert
Daniel Holbert
Andrew McCreight
Nicholas Hurley
Patrick Brosset
Phil Ringnalda
Daosheng Mu
Eric Rahm
Brendan Dahl
ffxbld
Dale Harvey
Dragana Damjanovic
Carsten "Tomcat" Book