An `sy-tp6` variant is added to the AWSY test suite that runs against the tp6 pageset.
Differential Revision: https://phabricator.services.mozilla.com/D24585
--HG--
extra : moz-landing-system : lando
This adds a '--tp6' option to `mach awsy-test` which allows the running of the AWSY test against the tp6 pageset rather than the default tp5 pageset.
Differential Revision: https://phabricator.services.mozilla.com/D23606
--HG--
extra : moz-landing-system : lando
It's possible for the first tab handle to change as well. This removes the special case for when we only add a new tab and just checks all the time.
Differential Revision: https://phabricator.services.mozilla.com/D25327
--HG--
extra : moz-landing-system : lando
This adds support for specifying per-suite perfherder alert thresholds and
updates the base content JS measurement to specify a 0.25% threshold.
Differential Revision: https://phabricator.services.mozilla.com/D21292
--HG--
extra : moz-landing-system : lando
Before this change, testing/awsy had 94 errors and testing/geckodriver had 17. The errors have been resolved
Differential Revision: https://phabricator.services.mozilla.com/D14712
--HG--
extra : moz-landing-system : lando
It's useful to get DMD reports even if we end up with negative
heap-unclassified. This catches any assertions during processing and makes
sure we move the reports to the upload dir even if there's a failure.
--HG--
extra : rebase_source : 3268d7b8f7f33c36c9b59bfdd5f181d80a0c4201
Bug 1506643 disabled the usage of "about:newtab". But it's
actually needed by awsy for testing the memory consumption
of Firefox.
Differential Revision: https://phabricator.services.mozilla.com/D11932
--HG--
extra : moz-landing-system : lando
This bumps the timeout when waiting for reports to 180 seconds which seems to
be long enough for MacOS in automation.
--HG--
extra : rebase_source : 6eb396e53bd37f6640b7c5402fb997c73af40d99
This will split out AWSY results with DMD enabled from standard results, thus
avoiding confusion due to a large discrepency in values due to DMD's overhead.
--HG--
extra : rebase_source : d301fbe0161914486d5269803b86d376627f8419
Disabling sandboxing seems to cause a memory regression for win32 builds which
affects our AWSY numbers. This switches over to only disabling sandboxing if
using a DMD build so that we can still run without crashing.
--HG--
extra : rebase_source : 9887c19cdd746aec9f6d9e64561f2226cd1ce443
This adds support running AWSY with DMD in automation via mozharness. We use
existence of dmd.py to detect whether or not dmd should be enabled.
Additionally sandboxing has to be disabled in order to avoid crashes on Windows
and OSX.
--HG--
extra : rebase_source : 1576dbb98bc2cff565ea5055daaec5a44aed88a8
We need testvars for the base case as well.
--HG--
extra : rebase_source : 0fbe7b3e206262d47f78e1289dceb02878ad987b
extra : histedit_source : fd1eabcc887e91dff8f4ec2e00b03fcd8bb68c9b
This adds support for only gathering data for a given process type. It also
allows you to limit the number of processes included in a measurement.
--HG--
extra : rebase_source : f4c172ff151f6739f0222f0e1c36bc299fe1d3d7
You can still run them on a --disable-stylo build, as long as that works
(presumably not for long).
I think I haven't missed anything, but please double-check.
MozReview-Commit-ID: 3BIAEjgTLo5
This patch was autogenerated by my decomponents.py
It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.
It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <![CDATA[, """ or '''. The first two
cover comments, the third one covers JS, the fourth covers JS embedded
in XUL, and the final two cover JS embedded in Python. This also
applies if the removed line was the first line of the file.
It covers the pattern matching cases like "var {classes: Cc,
interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove
the entire thing if they are all either Ci, Cr, Cc or Cu, or it will
remove the appropriate ones and leave the residue behind. If there's
only one behind, then it will turn it into a normal, non-pattern
matching variable definition. (For instance, "const { classes: Cc,
Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes
"const CC = Components.Constructor".)
MozReview-Commit-ID: DeSHcClQ7cG
--HG--
extra : rebase_source : d9c41878036c1ef7766ef5e91a7005025bc1d72b
This makes things slightly more inconvenient (having to set two
environment variables instead of one for the simplest case) until a few
patches down the line, when DMD is statically linked, at which point it
will get down to one environment variable every time.
--HG--
extra : rebase_source : 08dc3c05318b572ae1026227d0369fa8bf21b20f
This makes things slightly more inconvenient (having to set two
environment variables instead of one for the simplest case) until a few
patches down the line, when DMD is statically linked, at which point it
will get down to one environment variable every time.
--HG--
extra : rebase_source : 08dc3c05318b572ae1026227d0369fa8bf21b20f
This runs the DMD files through the DMD stack fixer so that we end up with
usable stacks instead of just offsets into libxul.
--HG--
extra : rebase_source : 486a9e0f97e9a0b5374784c8c5986449a7c12478
Adds logic to copy the DMD files that are generated in the temp dir to the
proper results dir.
--HG--
extra : rebase_source : 25ec05673db10654b86004e820bac1628c8a2382
This adds a '--dmd' param to the |mach awsy-test| command. It checks that the
build is in fact a DMD build and then adds the appropriate env vars to run with
DMD enabled.
--HG--
extra : rebase_source : 944fbe847ea22d4980f79333c0d86c0c490cefea