This patch adds a new layer to mozperftest that allows people to run all the tests that produced an alert locally.
It does this by querying Treeherder for the alert information, and determining the tests to run from there. A `--alert-exact` option is added to enable users to run the exact same command as was run in CI as well. This is done by querying the task information of the alerting task, and parsing the options from it in a framework-specific manner.
All harnesses have option parsing implemented for them, however some of them, such as AWSY are more manual due to how the argument parser is implemented in that harness.
Differential Revision: https://phabricator.services.mozilla.com/D219965
This patch changes how the coveragerc file is handled between raptor, and mozperftest unit test runs. Instead of using a single file, this patch adds a second one that is specific to raptor, and renames the original to `.mpt-coveragerc`.
Differential Revision: https://phabricator.services.mozilla.com/D219964
This patch adds a new layer to mozperftest that allows people to run all the tests that produced an alert locally.
It does this by querying Treeherder for the alert information, and determining the tests to run from there. A `--alert-exact` option is added to enable users to run the exact same command as was run in CI as well. This is done by querying the task information of the alerting task, and parsing the options from it in a framework-specific manner.
All harnesses have option parsing implemented for them, however some of them, such as AWSY are more manual due to how the argument parser is implemented in that harness.
Differential Revision: https://phabricator.services.mozilla.com/D219965
This patch changes how the coveragerc file is handled between raptor, and mozperftest unit test runs. Instead of using a single file, this patch adds a second one that is specific to raptor, and renames the original to `.mpt-coveragerc`.
Differential Revision: https://phabricator.services.mozilla.com/D219964
First and foremost, this undoes the patch for bug 1845125, which causes
other problems (e.g. output being dropped past a certain point).
The rest of the patch addresses bug 1845125 at the root: Ultimately, this
is a similar problem to bug 1863675.
wait is blocked on joining the stream reader thread, but the stream
reader thread is blocked on readline because the process is finished but
hasn't been waited on yet.
So joining the stream reader thread after the process is known to have
been finished is expected to work more reliably... except when a child
has been spun up that keeps it alive. In this case, we just keep the
reader thread working in the background, which is a similar strategy to
what was done in bug 1863675.
Differential Revision: https://phabricator.services.mozilla.com/D218389
As js has different flags compared to the remaining parts of the
codebase, set a specific variable (namely MOZ_JS_OPTIMIZE_FLAGS) and use
it instead of MOZ_OPTIMIZE_FLAGS using a specific hook in
python/mozbuild/mozbuild/frontend/context.py
Also:
- harmonize moz_optimize_flags type to always return a list.
- moz_optimize now either returns "1" or None (no use case distinguishes
between returning 1 or 2)
Differential Revision: https://phabricator.services.mozilla.com/D216098
As js has different flags compared to the remaining parts of the
codebase, set a specific variable (namely MOZ_JS_OPTIMIZE_FLAGS) and use
it instead of MOZ_OPTIMIZE_FLAGS using a specific hook in
python/mozbuild/mozbuild/frontend/context.py
Also:
- harmonize moz_optimize_flags type to always return a list.
- moz_optimize now either returns "1" or None (no use case distinguishes
between returning 1 or 2)
Differential Revision: https://phabricator.services.mozilla.com/D216098
The [tab-close-button](https://searchfox.org/mozilla-central/rev/f9157a03835653cd3ece8d2dc713a782b7e4374e/browser/base/content/tabbrowser-tab.js#40) is not labeled and is missing an interactive role of button, while it is functioning as one.
Note: we do not want this control to be keyboard focusable, because keyboard-only user could close the tab via the context menu and we don't want to create an additional tab stop for the navigation as well, but making sure the control is marked up as a button with an accessible name would allow it to be actionable with speech-to-text software, with touch devices, with switch controls in scan mode, and for screen readers via their navigation shortcuts as well.
Differential Revision: https://phabricator.services.mozilla.com/D204413
This patch modifies the background-resource (formerly background-cpu) android test to collect resource information at distinct times rather than only at the end of the test run.
The collection script is split in two here for cpu, and memory. The python parsing script is also modified to be able to gather the resources from multiple files, and the name is changed to better reflect what it does.
This patch also renames the test to better reflect that it's a resource usage test and not just a cpu test.
Differential Revision: https://phabricator.services.mozilla.com/D217097
One notable change in this patch: a code path that checks for pre-existing distribution.ini and .desktop files.
If you place a distribution.ini or .desktop file in the root of any of the Linux .deb templates directories (paths specified in deb-templates and deb-l10n-templates), the supplied file will be used instead of generating or downloading a default file.
Differential Revision: https://phabricator.services.mozilla.com/D211141
