This adds the app.update.checkInstallTime pref with a value of false in all tests that have the app.update.disabledForTesting pref except for geckodriver which is covered by bug 1508283.
This patch moves all the logic we currently have
baked-in JsTerm to handle the autocompletion data:
- deciding to fetch from the server or the cache
- handling concurrent requests
- managing the cache.
This is now done through dedicated Redux actions and reducers.
In the JsTerm, where the autocompletePopup still lives, we
handle those data changes in componentWillReceiveProps.
Some tests were modified in order to pass with these changes.
Differential Revision: https://phabricator.services.mozilla.com/D11454
--HG--
extra : moz-landing-system : lando
We used to have animations during tab opening/closing, but this was introducing
intermittents as we were not correctly waiting for animation's end.
MozReview-Commit-ID: 2mscsA8Uosd
Differential Revision: https://phabricator.services.mozilla.com/D10263
--HG--
extra : moz-landing-system : lando
This seems to silence the intermittent, even though it doesn't explain
why we started spiking after moving TabClient to a Front.
Differential Revision: https://phabricator.services.mozilla.com/D9755
--HG--
extra : moz-landing-system : lando
The biggest change here is that the tart.html page that drives the
test (not to be confused with the pages loaded in new tabs during the
test) moves from a chrome: page inside the extension to a regular http:
page. That also required revamping the communication between tart.html
and the extension. The rest of the changes are just the packaging and
startup mechanics for the test extension.
Differential Revision: https://phabricator.services.mozilla.com/D8807
--HG--
rename : testing/talos/talos/tests/tart/addon/bootstrap.js => testing/talos/talos/tests/tart/addon/api.js
rename : testing/talos/talos/tests/tart/addon/content/blank.icon.html => testing/talos/talos/tests/tart/addon/chrome/blank.icon.html
rename : testing/talos/talos/tests/tart/addon/install.rdf => testing/talos/talos/tests/tart/addon/manifest.json
rename : testing/talos/talos/tests/tart/addon/content/tart.html => testing/talos/talos/tests/tart/tart.html
rename : testing/talos/talos/tests/tart/addon/content/tart.ico => testing/talos/talos/tests/tart/tart.ico
extra : source : 3133f6ab1bd8ea2aa261f8e9024ab3fb8eb0ddcb
This is to know if DAMP works without e10s shims.
MozReview-Commit-ID: 2IZGlenkuzb
Differential Revision: https://phabricator.services.mozilla.com/D8839
--HG--
extra : moz-landing-system : lando
I'm not sure at which point this broke, but the current dump_syms_mac exits with
an error when it's run on a XUL binary on my machine.
MozReview-Commit-ID: 8nV7n7G5MKS
--HG--
extra : rebase_source : e84810e6df0767c206f0a61986a5403577845a85
extra : amend_source : 107e41210966c79022391a89d98b976f2ae2ab4a
This gets accessed in beta simulations since xperf has been enabled on Windows 10.
Differential Revision: https://phabricator.services.mozilla.com/D8516
--HG--
extra : moz-landing-system : lando
This is a pretty straightforward conversion. We deliberately continue
to use chrome: urls in this test since those are loaded in the parent
process so test measurements will not include additional noise from
IPC to a content process.
--HG--
rename : testing/talos/talos/tests/tresize/addon/bootstrap.js => testing/talos/talos/tests/tresize/addon/api.js
rename : testing/talos/talos/tests/tresize/tresize-test.html => testing/talos/talos/tests/tresize/addon/chrome/tresize-test.html
rename : testing/talos/talos/tests/tresize/addon/install.rdf => testing/talos/talos/tests/tresize/addon/manifest.json
extra : rebase_source : d5449086194225b737c70885881ac297d3c4ecb6
Some new features were added to MozAfterPaint events in bugs 1264409 and
1264798 to allow tests to make more accurate measurements. Updating
tresize to use these features is not directly related to the main goal
of this bug, but lets do it anyway while we're touching tresize...
--HG--
extra : rebase_source : ba966b0f22c1ceb7fa1a747e75b159a30997929f
The talos tresize test was originally written as a "startup" test which
is confusing since it doesn't measure anything that happens during
browser startup. Convert it here to the "pageloader" style, which
mostly involves moving files around, also some changes to how the test
results are reported to the Talos framework.
--HG--
rename : testing/talos/talos/startup_test/tresize/addon/bootstrap.js => testing/talos/talos/tests/tresize/addon/bootstrap.js
rename : testing/talos/talos/startup_test/tresize/addon/chrome.manifest => testing/talos/talos/tests/tresize/addon/chrome.manifest
rename : testing/talos/talos/startup_test/tresize/addon/content/Profiler.js => testing/talos/talos/tests/tresize/addon/content/Profiler.js
rename : testing/talos/talos/startup_test/tresize/addon/content/framescript.js => testing/talos/talos/tests/tresize/addon/content/framescript.js
rename : testing/talos/talos/startup_test/tresize/addon/content/tresize.js => testing/talos/talos/tests/tresize/addon/content/tresize.js
rename : testing/talos/talos/startup_test/tresize/addon/install.rdf => testing/talos/talos/tests/tresize/addon/install.rdf
rename : testing/talos/talos/startup_test/tresize/addon/content/tresize-test.html => testing/talos/talos/tests/tresize/tresize-test.html
extra : rebase_source : a242750692e7449788cf58d620b24bffc53a32ff
tresize-test.html attempts to load
"resource://talos-powers/TalosPowersContent.js", but this might not be available
yet if the tresize add-on hasn't loaded. This patch changes the location of this
resource to a relative path, which should always be available. Additionally,
this patch awaits on TalosPowers.loadPromise before using talos APIs.
Differential Revision: https://phabricator.services.mozilla.com/D7312
--HG--
extra : moz-landing-system : lando
