Previously we set use_v8_context_snapshot to false to speed up build
times and be consistent with all platforms (since for some platforms
this was perma/highly intermittent e.g. win/linux, and others taking a
very long time e.g. arm mac cross build)
cstm-car-m tests have been perma failing recently (sometime between June
10th & 11th). Enabling this flag seems to help, but it is presently
unclear why that is, and why other platforms were not affected.
Differential Revision: https://phabricator.services.mozilla.com/D214257
We wanted to have a temporary workaround to explicitly allow/block
domains to use MFCDM due to the bug 1901334. As this is only a
workaround, we'd like to do it in a simplest way in order to save our
resource.
Our strategy is to keep Nightly unfiltered so that we could discover
more websites affected by the CSS problem. On other channels, we would
currently only allow Netflix to use MFCDM as we have been testing
with them and know that issue won't affect them.
We will first try to use the allow list first to ensure the MFCDM
playback quality, and gradually switch to the block list to enable the
MFCDM ability to more websites.
Differential Revision: https://phabricator.services.mozilla.com/D213820
Before trying to address the issue in depth (possibly backporting an
upcoming llvm-config change), let's just revert to something that is
known to work for the moment.
Differential Revision: https://phabricator.services.mozilla.com/D213529
Upstream changes have changed the config path of depot_tools to default
to `$HOME/.config`. Instead we also have the option to set
`$XDG_CONFIG_HOME`. At the moment this only affects linux, with
windows/macos slated to have a similar change soon with possibly
different setup.
Differential Revision: https://phabricator.services.mozilla.com/D213438
Looks like kaniko now handles VOLUME instructions before anything else,
so by the time we get to RUN mkdir, /build already exists.
Differential Revision: https://phabricator.services.mozilla.com/D213061
Skip running the indexing tasks if they already ran on the same revision
and the previous decision task expires in over a week.
Differential Revision: https://phabricator.services.mozilla.com/D213466
The video under test is a simple recording of solid colors, where the
first frame is red, second frame is blue, subsequent frames alternate
between green and purple, and the final frame is yellow. This allows us
to identify what frame is being displayed and when in a browser agnostic
way.
This is achieved by updating the visualmetrics python script in
browsertime to identify frames which match a given color range, called
key color frames. The script will produce a list of which frames appear
when that we can use to estimate the playback latency. Note that the
annotated videos produced by the jobs will also be annotated to make it
clear which frames it believes are key color frames.
Until the tests have proven stable, they have been set at tier 3.
The status of the merge can be seen at:
https://github.com/sitespeedio/browsertime/pull/2119
Differential Revision: https://phabricator.services.mozilla.com/D210242
Until recently, beta-YYYY-MM-DD dated channels was the only way to get
specific betas, but now it's possible to use x.y.z-beta.n, but
repack_rust.py doesn't handle that string as a version.
By considering only channels starting with beta- or nightly to be dated,
we allow x.y.z-beta.n to be considered as a version.
Differential Revision: https://phabricator.services.mozilla.com/D213367
When building cargo sets up the patches for the vendored dependencies of
libstd, when several of those dependencies are different versions of the
same crate, only one of the corresponding patches work because the
package name, derived from the directory name, doesn't match.
Instead, we always take the package name from Cargo.toml.
While we're here, we add the missing resources on the rust-dev tasks.
Differential Revision: https://phabricator.services.mozilla.com/D213380
This patch sets things up such that the new non VM pool is used by default, and
current tasks can explicitly opt into using the old virtualbox based pool.
The taskgraph --diff of this change is identical, but this will allow us to
easily move tasks over to the new pool as they are ready.
Differential Revision: https://phabricator.services.mozilla.com/D212601
This patch contains everything we need to flip all the l10n consumers in the tree to the new github repository:
* Enable fetching strings for builds (`desktop_l10n.py` for Desktop, `android-mozharness-build.json` for Android)
* l10n bumper (`l10n-bump/kind.yml`)
* merge automation (`merge-automation/kind.yml`)
* deb repackages (`repackaging/deb.py`)
* Switch `l10n-changesets` files to git refs to avoid breaking repacks before l10n bumper runs
This will need a final update because it will no doubt be bitrotted by the l10n bumper.
Differential Revision: https://phabricator.services.mozilla.com/D212462
This patch adds a new background resource usage test that will run through mozperftest. The test starts the Fenix application, and then backgrounds it for 10 minutes to measure the CPU, and memory usage throughout that time. The hook is used to setup the xmlstarlet tool.
Differential Revision: https://phabricator.services.mozilla.com/D212630
This patch replaces the chromedrivers retrieved from the chromium
snapshots with the Chrome for Testing (CfT) chromedrivers (through the
"Canary" channel) for our Chromium-as-Release tests.
There is an occasional intermittent issue that occurs where the
chromedriver from the snapshots don't always work. Instead we can use
the `last-known-good-versions-with-downloads.json` provided by CfT to
get guaranteed stable chromedrivers.
Differential Revision: https://phabricator.services.mozilla.com/D212707
- Sample 2k crashes, 500 for each release channel, this is somewhat slow as
we're not using an API token (but we can add it later)
- Use dump_syms' logic to fetch the files from the symbol servers, rather than
using the Python logic
- Fail hard if one of the steps fail, including unexpected dump_syms crashes
- Print out a summary of all the actions that have been taken
Differential Revision: https://phabricator.services.mozilla.com/D212692
Building rustfmt would fail regularly, so the option was added to ignore
the problem, but that presumably hasn't been the case in a while.
The option was removed in rustc 1.80.
Differential Revision: https://phabricator.services.mozilla.com/D212491
This patch adds a lull-schedule attribute to some browsertime live-site tasks so that we can start testing lull-scheduling. The lull-schedule attribute will be used to denote how frequently a particular task should run. The lull-schedule attribute exists first as a raptor specific setting, and is then added to the `extra` section so that we can make use of it in the `mozci` module.
Differential Revision: https://phabricator.services.mozilla.com/D212202
This is prep work for enabling pulling l10n strings from github. When we do that, we'd like to start bumping the mobile changesets file alongside the desktop one. At the moment it simply pulls `default` for all revisions.
Differential Revision: https://phabricator.services.mozilla.com/D212431
Also:
- deactivate LLVM_SYMBOLIZER on android mozconfig as we don't cross compile it yet.
- enforce LLVM_SYMBOLIZER when fuzzing is on
- fix osx packaging to include llvm-symbolizer when fuzzing, and provide
it through tc
Differential Revision: https://phabricator.services.mozilla.com/D210190
This patch adds a layer to setup the binary, and provide a single interface for specifying it and using it through the metadata. At the same time, some changes were made to the perfherder metrics production to gather the application name, and version from the metadata. The intermediate results are also properly passed into the perfherder blob production step as they were previously being ignored.
Differential Revision: https://phabricator.services.mozilla.com/D211738
These tasks will never fail, and don't have logs, so having them on
treeherder can be confusing.
Rename `post-signing` to `post-signing-dummy` to benefit from the
special handling in `verify_dependency_tiers`.
Differential Revision: https://phabricator.services.mozilla.com/D211746
Chrome responsiveness test have been running every Monday, Wednesday, and Friday on the general_perf_testing cron
We have been exeriencing issues with these tests, and this patches disables their running on the GPT cron
Differential Revision: https://phabricator.services.mozilla.com/D211279
As part of our okr goals of being competative in pageload we are running essential pageload tests on chrome on android to have an idea of how we compare to chrome on android
Differential Revision: https://phabricator.services.mozilla.com/D209981