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
Steve Fink
Joel Maher
Alexandru Michis
Sebastian Hengst
Frederik Braun
Alex Ionescu
sotaro
Butkovits Atila
Ryan VanderMeulen
Alex Lopez
Andrew Halberstadt
Mike Hommey
Emilio Cobos Álvarez
Andi-Bogdan Postelnicu
june wilde
Cosmin Sabou
Gregory Mierzwinski
Julien Cristau
Dave Hunt
Bogdan Tara
Ben Hearsum
Mark Banner
Christian Holler
Julian Seward