We don't offer API splits any more, and with the separation of GeckoView with
the rest of the front-end it's increasingly unlikely that we will in the
future.
This change makes it so that the build name doesn't contain the API version so
that we can update it without breaking all the automation that relies on the
build name.
Differential Revision: https://phabricator.services.mozilla.com/D114369
This adds the following tasks on central:
+test-linux1804-64-asan-qr/opt-mochitest-webgl1-core-fis-gli-e10s
+test-linux1804-64-qr/debug-mochitest-webgl1-core-fis-gli-e10s
+test-linux1804-64-shippable-qr/opt-mochitest-webgl1-core-fis-gli-e10s
+test-macosx1015-64-qr/debug-mochitest-webgl1-core-fis-gli-e10s
+test-macosx1015-64-shippable-qr/opt-mochitest-webgl1-core-fis-gli-e10s
+test-windows10-64-qr/debug-mochitest-webgl1-core-fis-gli-e10s
+test-windows10-64-shippable-qr/opt-mochitest-webgl1-core-fis-gli-e10s
And the following tasks on autoland:
+test-linux1804-64-asan-qr/opt-mochitest-webgl1-core-fis-gli-e10s
+test-linux1804-64-qr/debug-mochitest-webgl1-core-fis-gli-e10s
+test-linux1804-64-qr/opt-mochitest-webgl1-core-fis-gli-e10s
+test-macosx1015-64-qr/debug-mochitest-webgl1-core-fis-gli-e10s
+test-macosx1015-64-qr/opt-mochitest-webgl1-core-fis-gli-e10s
+test-windows10-64-qr/debug-mochitest-webgl1-core-fis-gli-e10s
+test-windows10-64-qr/opt-mochitest-webgl1-core-fis-gli-e10s
Differential Revision: https://phabricator.services.mozilla.com/D116832
This adds the set of macosx1015-qr tests to ccov in the full taskgraph (and
removes the 1014 set which is just TV). Since these task weren't running
anywhere it has no impact on target task graphs.
I didn't bother testing on try since they aren't running there anyway. So have
no idea if this change introduces new failures. But if we cared about that we
would be running them ;).
Differential Revision: https://phabricator.services.mozilla.com/D116395
This makes the following changes on autoland:
+test-linux1804-64-asan/opt-mochitest-browser-chrome-fis-e10s
And the following changes on central:
+test-linux1804-64-asan/opt-mochitest-browser-chrome-fis-e10s
Differential Revision: https://phabricator.services.mozilla.com/D116623
This makes the following changes on autoland:
+test-linux1804-64/opt-mochitest-browser-chrome-fis-e10s
+test-macosx1015-64-qr/debug-mochitest-browser-chrome-fis-e10s
+test-macosx1015-64-qr/opt-mochitest-browser-chrome-fis-e10s
+test-windows10-64-qr/debug-mochitest-browser-chrome-fis-e10s
+test-windows10-64-qr/opt-mochitest-browser-chrome-fis-e10s
And the following changes on central:
+test-macosx1015-64-qr/debug-mochitest-browser-chrome-fis-e10s
+test-macosx1015-64-shippable-qr/opt-mochitest-browser-chrome-fis-e10s
+test-windows10-64-qr/debug-mochitest-browser-chrome-fis-e10s
-test-windows10-64-shippable/opt-mochitest-browser-chrome-fis-e10s
Differential Revision: https://phabricator.services.mozilla.com/D116277
We got multiple instances of confusion because nightly builds were
signed with a new GPG key, but it was not published in an obvious place.
We already publish this alongside every beta and release candidate, as
well as to a GPG keyserver - but if you're just looking at nightly
builds, it's unclear what you should be verifying them with.
Differential Revision: https://phabricator.services.mozilla.com/D116385
This helps hint that in some cases, a user may have forgotten to diff
with `-J` if they were changing task bodies/payloads instead of adding
or removing a task.
Differential Revision: https://phabricator.services.mozilla.com/D116384
The decision task started to complain about the macOS ccov build setting up the
environment to export tests but not doing so. Previous tasks exported tests and
there are no recent changes altering this.
This enables the following tasks on autoland:
+test-linux1804-64/opt-mochitest-devtools-chrome-fis-e10s
+test-windows10-64/debug-mochitest-devtools-chrome-fis-e10s
+test-windows10-64/opt-mochitest-devtools-chrome-fis-e10s
and the following tasks on central:
+test-windows10-64/debug-mochitest-devtools-chrome-fis-e10s
Differential Revision: https://phabricator.services.mozilla.com/D116160
Without exporting org.mozilla.firefox.<profile_name> interface to the session bus
the Firefox cannot use the remote to open the links in the browser which
leads to running another instance showing the app is already running.
Differential Revision: https://phabricator.services.mozilla.com/D115817
At the same time, move the option to python configure, which changes how
to disable it (setting to an empty value rather than 0).
Differential Revision: https://phabricator.services.mozilla.com/D115844
TSan is prone to issues with slowdown and resource exhaustion. Increasing crashtest chunking appears to reduce the rate of restarts and intermittents related to timeouts.
Differential Revision: https://phabricator.services.mozilla.com/D110372
This adds the following tasks on central:
+test-linux1804-64-asan/opt-mochitest-webgl2-ext-fis-e10s
+test-linux1804-64-qr/debug-mochitest-webgl2-ext-fis-e10s
+test-linux1804-64-shippable-qr/opt-mochitest-webgl2-ext-fis-e10s
+test-windows10-64-shippable/opt-mochitest-webgl2-ext-fis-e10s
+test-windows10-64/debug-mochitest-webgl2-ext-fis-e10s
And the following tasks on autoland:
+test-linux1804-64-asan/opt-mochitest-webgl2-ext-fis-e10s
+test-linux1804-64-qr/debug-mochitest-webgl2-ext-fis-e10s
+test-linux1804-64-qr/opt-mochitest-webgl2-ext-fis-e10s
+test-windows10-64/opt-mochitest-webgl2-ext-fis-e10s
+test-windows10-64/debug-mochitest-webgl2-ext-fis-e10s
Differential Revision: https://phabricator.services.mozilla.com/D115214
This patch adds a new retrigger option to the backfill task so that we can prevent the perf sheriff bot from triggering tests on pushes which have already run those tests.
Differential Revision: https://phabricator.services.mozilla.com/D115057
As an intermediate step to allow mach commands as standalone functions, the MachCommandBase
subclass instance that currently corresponds to self has to be made available as a separate
argument (named command_context).
Differential Revision: https://phabricator.services.mozilla.com/D109650
This patch makes it possible to properly backfill vismet tasks. Backfilling a vismet task will now trigger a test task along with the vismet task so it doesn't rerun on the same data.
Differential Revision: https://phabricator.services.mozilla.com/D114645
Now that getHSTSPreloadList.js runs with increased parallelism, it goes
much faster and we don't need to let the task run for 6 hours.
The timeout was 3 hours for a while, then bumped to 5 hours in bug
1570646, then to 6 hours in bug 1705639 (with 250 in-flight requests).
The new run time with 500 in-flight requests seems to be around 2.5
hours, so pick 4 hours as a compromise.
Differential Revision: https://phabricator.services.mozilla.com/D114496
CLOSED TREE
Backed out changeset 7a4401a358e8 (bug 1639164)
Backed out changeset f1377ee7e2d2 (bug 1639164)
Backed out changeset f9c73976484d (bug 1639164)
Before this patch, getHSTSPreloadList.js would have no more than 250 requests
in flight at any given time. In the past, this limit was 500. After a refactor
that inadvertantly completely removed the limit, it was reduced to 250.
Presumably increasing it to 500 again will not have negative effects and will
allow the script to run faster.
Differential Revision: https://phabricator.services.mozilla.com/D114019
This enables the following tasks on central:
+test-linux1804-64-asan/opt-marionette-fis-e10s
+test-linux1804-64-qr/debug-marionette-fis-e10s
+test-linux1804-64/debug-marionette-fis-e10s
+test-windows10-64-qr/debug-marionette-fis-e10s
+test-windows10-64/debug-marionette-fis-e10s
And the following task on autoland:
+test-linux1804-64-asan/opt-marionette-fis-e10s
Differential Revision: https://phabricator.services.mozilla.com/D114154
The parallel run of sequences of "clean; clippy; clean" creates race
conditions that alter the results of clippy and can mask errors.
Moreover, chances are clippy is not allowing any parallelization
anyways, because with two concurrent clippy running, one will be waiting
for the other because of cargo locking.
This turns the current intermittent failure into a permanent one.
Differential Revision: https://phabricator.services.mozilla.com/D114209
This ensures that when your patch has an error, taskgraph generation will fail
faster rather than needing to wait for the base generation to complete.
Depends on D113854
Differential Revision: https://phabricator.services.mozilla.com/D113859
This will tie the version used for CI lints to the version of rust used
for builds on CI.
Bonus point: we can now have rustfmt and clippy on Windows and mac,
which allows to run the corresponding mozlint unit tests on those
platforms.
Differential Revision: https://phabricator.services.mozilla.com/D113905
This will warn if someone includes something like:
skip-if = <condition A> || <condition B> # reason A is skipped; reason B is skipped
Instead they should use:
skip-if =
<condition A> # reason A is skipped
<condition B> # reason B is skipped
Differential Revision: https://phabricator.services.mozilla.com/D113707
This patch enables the process-switch test on mozilla-central. It also adds a new field in the raptor manifest to specify whether or not zero-values in vismets can be accepted.
Differential Revision: https://phabricator.services.mozilla.com/D113221
Crashtests on Android in CI for SW-WR to get more testing coverage.
Problem of 1678938-1.html is going to be handled by bug 1704943.
Differential Revision: https://phabricator.services.mozilla.com/D112519
As an intermediate step to allow mach commands as standalone functions, the MachCommandBase
subclass instance that currently corresponds to self has to be made available as a separate
argument (named command_context).
Differential Revision: https://phabricator.services.mozilla.com/D109650
This adds the following configurations to central/autoland:
> test-linux1804-64-asan/opt-mochitest-webgl2-core-fis-e10s
> test-linux1804-64-qr/debug-mochitest-webgl2-core-fis-e10s
> test-linux1804-64-qr/opt-mochitest-webgl2-core-fis-e10s
> test-windows10-64-qr/debug-mochitest-webgl2-core-fis-e10s
> test-windows10-64-qr/opt-mochitest-webgl2-core-fis-e10s
Differential Revision: https://phabricator.services.mozilla.com/D112996
Now that docker images have been upgraded to Debian buster, we can
install a native zstd binary and use tar's native support rather than
relying on piping the output of tar to a python script that uses the
python-zstandard module. At least we can do that for toolchain tasks
that run on such docker images, which also means we can't on Mac and
Windows.
Differential Revision: https://phabricator.services.mozilla.com/D112894
This adds the following tasks on central:
> test-linux1804-64-shippable-qr/opt-mochitest-webgl1-ext-fis-e10s
> test-windows10-64-shippable-qr/opt-mochitest-webgl1-ext-fis-e10s
Differential Revision: https://phabricator.services.mozilla.com/D112983
This adds the following tasks on autoland and central (except shippable there):
> test-linux1804-64-qr/debug-mochitest-webgl1-ext-fis-e10s
> test-linux1804-64-qr/opt-mochitest-webgl1-ext-fis-e10s
> test-windows10-64-qr/debug-mochitest-webgl1-ext-e10s
> test-windows10-64-qr/debug-mochitest-webgl1-ext-fis-e10s
> test-windows10-64-qr/opt-mochitest-webgl1-ext-e10s
> test-windows10-64-qr/opt-mochitest-webgl1-ext-fis-e10s
Note this include the non-fission versions on Windows 10 due to our use of
'built-projects' and not previously running these tests on windows-qr.
Differential Revision: https://phabricator.services.mozilla.com/D112620
If I'm reading compiler-rt correctly, this and __lsan_default_options
should be additive so we shouldn't need to specify the allow_leaks flag
gobally.
Differential Revision: https://phabricator.services.mozilla.com/D110699
As an intermediate step to allow mach commands as standalone functions, the MachCommandBase
subclass instance that currently corresponds to self has to be made available as a separate
argument (named command_context).
Differential Revision: https://phabricator.services.mozilla.com/D109650
Updating the HSTS preload list is now taking close to the previous limit
of 5 hours, so bump it to 6 hours as a stopgap, and adjust the start
time to keep its end time from going too late in the day.
Differential Revision: https://phabricator.services.mozilla.com/D112346
1. Add task to get and build clang from the main branch.
2. Using clang main toolchain we build on a daily basis linux64 firefox, this tasks also automatically triggers the fetch and build of clang from main branch since we don't cache it.
Differential Revision: https://phabricator.services.mozilla.com/D111063
This patch enables Ion by default as the optimising compiler for wasm on
AArch64, and disables Cranelift. Cranelift is still available if the build is
configured with --enable-cranelift. In that case, *only* Cranelift is
available. There are no configuration flags to enable both Ion and Cranelift
simultaneously.
This mostly reverts the Phase 0 and Phase 1 patches that are bug 1678097
D102420 and D101867 respectively.
The command line option --wasm-force-ion has been removed.
With this patch in place, users of the shell should specify
`--wasm-compiler=optimizing` to get an optimising wasm compiler. Which one is
provided depends on the configuration options as described above.
`--wasm-compiler=cranelift` and `--wasm-compiler=ion` are now only accepted
when the relevant compiler has been enabled, and so neither is a "safe" way to
request an optimising tier.
For that reason, test directories that previously requested
also-with-Ion-please by stating `test-also=--wasm-compiler=ion;` in their
`directives.txt` file, have been changed to use
`test-also=--wasm-compiler=optimizing;`.
In places where the JSContextOptions are set, the non-selected compiler (Ion
or CL) is explicitly set to `false` (eg, `.setWasmIon(false)`). This may be
overly conservative, but seems wise given that it's not immediately obvious
what the previous value of that flag is, and given the recent difficulties
with incorrect option propagation/handling (eg, bug 1697560).
Differential Revision: https://phabricator.services.mozilla.com/D101695
At least in the 'test' kind, this is causing the keyed_by dicts to get very
complex as we need to ensure that each task is only matched by a single regex.
Instead, this makes them act more like case / match statements where the first
arm that matches the task will be used.
Differential Revision: https://phabricator.services.mozilla.com/D111727
Fixed browsertime benchmark script to correctly run the tests, fix python code to collect all the pagecycles data and disable unity-webgl test running on windows7.
Differential Revision: https://phabricator.services.mozilla.com/D110683
Add HttpChannelCompletion, which is just the completion time for any request.
This allows us to measure overall improvements, instead of shifting requests from cache to network via RCWN.
Differential Revision: https://phabricator.services.mozilla.com/D111335