This will make sure that when running |mach python-test --python 3| locally,
we only run the tests that also run in CI with python 3 (and therefore pass
presumably).
MozReview-Commit-ID: 3OBr9yLSlSq
--HG--
extra : rebase_source : 456340d0ecdddf1078f2b5b4ebb1eddf3813b26a
The term "tab actor" was used ambiguously to mean either the "target actor
representing a tab" or "a child actor of the tab target actor" (such as the
console actor). Here we rename the second case to "target-scoped actor".
Differential Revision: https://phabricator.services.mozilla.com/D1760
--HG--
rename : devtools/client/debugger/test/mochitest/browser_dbg_tabactor-01.js => devtools/client/debugger/test/mochitest/browser_dbg_target-scoped-actor-01.js
rename : devtools/client/debugger/test/mochitest/browser_dbg_tabactor-02.js => devtools/client/debugger/test/mochitest/browser_dbg_target-scoped-actor-02.js
browser-idle-startup-tasks-finished will kick off some caching that can influence
future runs in the same profile. We want to make sure that we properly create
that cache when running Talos.
MozReview-Commit-ID: 9Ydt1ur3tsj
--HG--
extra : rebase_source : 059fea98d2c77c7a89e36dff7b6c85dfee3f6e57
goQuitApplication does the work of closing all windows anyways, so closing the
window is superfluous. goQuitApplication is also going to be checking for certain
operations to be finished before doing that, which could be influenced by closing
a window early.
MozReview-Commit-ID: 9gJ0ZRn753F
--HG--
extra : rebase_source : bcf902e332fd6a5aa82e40933e6b5d15c0f73cea
When running talos locally with --geckoProfile set, the latest gecko-profile archive will automatically be loaded in perf-html.io using the view-gecko-profile tool. To disable this automatic perf-html.io launching, set TALOS_DISABLE_PROFILE_LAUNCH=1.
MozReview-Commit-ID: 8tpLnsPAXD9
--HG--
extra : rebase_source : 66d03b55103e9771c4c8c4c70ff67212f24c1124
This moves all of the global prefs that were previously defined
in testing/talos/talos/config.py, into a new "perf" profile under
testing/profiles/perf/user.js.
This perf profile will be shared with raptor, so changes to one
framework will result in changes to the other.
MozReview-Commit-ID: JRxZEDlPu6b
--HG--
extra : rebase_source : 38f61eb6f9dd3e8dd9e0425ffe32dbdf845fcf65
This makes debugging failures extremely difficult, and tends to confuse
developers who add debugging logs and can't understand why they're not showing
up.
MozReview-Commit-ID: Wajt2JczuY
--HG--
extra : rebase_source : 497d78a915ad92707ba5f7d5b437ec1dfbc5b8f8
This is based on a script I'd already created to migrate test extensions to
the JSON format we use to generate fixture add-ons.
The delay update add-ons used invalid XML in their manifests, which the
built-in parser ignored but the new parser doesn't accept, so I had to fix
those, too.
MozReview-Commit-ID: BnuxZiBhhJL
--HG--
rename : toolkit/mozapps/extensions/internal/UpdateRDFConverter.jsm => toolkit/mozapps/extensions/internal/RDFManifestConverter.jsm
extra : source : 292cf80054b4734a0d7c84e987f68e229f2ccc24
extra : histedit_source : 1072def8a28149a9f9882825f73435336b205072%2C2c72e58aa973fe24867868d06dcc63235dd68da2
This also removes any redundant Ci.nsISupports elements in the interface
lists.
This was done using the following script:
acecb401b7/processors/chromeutils-generateQI.jsm
MozReview-Commit-ID: AIx10P8GpZY
--HG--
extra : rebase_source : a29c07530586dc18ba040f19215475ac20fcfb3b
The test was measuring the time spent to expand an object only
containing alphanumeric properties. But due to how we fetch properties,
this only cover a part of data fetching performances.
This patch adds numeric and Symbol indexes in order to have a more precise
view of what is happening when expanding an object in the console.
MozReview-Commit-ID: AwSRLwnC35T
--HG--
extra : rebase_source : 0cc2a9502ca739956de7371cf288b6e9bbc446a7