Temporary add-ons were already ignored by the `isRecommended` getter of
`AddonWrapper, but they were still read and parsed, and consequently
resulted in unnecessary warning messages in the console.
This patch stops with warning about IO errors (because those are
expected for the majority of cases), and only logs a warning if there is
an actual parser error.
Differential Revision: https://phabricator.services.mozilla.com/D36987
--HG--
extra : moz-landing-system : lando
Only enabled on try/m-c as tier-2 for now, per email discussion, to minimize
load on bitbar Pixel 2 devices.
Depends on D36799
Differential Revision: https://phabricator.services.mozilla.com/D36800
--HG--
extra : moz-landing-system : lando
Due to the sheer number of tests that exhibit a random fuzz with maxDifference=1
and maxDifference=2 with WR on Android, it's easier to just tweak the harness
to autofuzz these away. This adds machinery to do so, and also adds a new
annotation that can be used to disable the autofuzzing on specific tests.
Depends on D36794
Differential Revision: https://phabricator.services.mozilla.com/D36796
--HG--
extra : moz-landing-system : lando
With this patch, all android power tests (idle, idle-bg, and speedometer) will only run once a week, through cron, on saturday.
Differential Revision: https://phabricator.services.mozilla.com/D36827
--HG--
extra : moz-landing-system : lando
Ensure source links for selectors in the Rules view and warning links in Web Console for minified CSS go to the right location in the Style Editor after applying automatic prettification.
This only works for linked stylesheets. [Bug 1169770](https://bugzilla.mozilla.org/show_bug.cgi?id=1169770) needs to be fixed first before this can work correctly on inline minified stylesheets.
This patch augments the `prettifyCSS()` method to generate the mappings necessary to generate a sourcemap from the original to the prettified source. It uses these mappings to translate the cursor position when invoking the Style Editor to be opened at a specific location.
The mappings from the minified to the prettified source are used only until the stylesheet is changed in the Style Editor. Upon editing the source in the Style Editor, the associated mappings are cleared because it's likely they have been rendered invalid.
The updated stylesheet will already be prettified so it bypasses the `prettifyCSS()` method, thus avoiding the need to re-generate mappings. New CSS warnings will be listed in the Web Console which point to the right location in the edited stylesheet (the old warnings no longer point to the right place, but that's an acceptable side-effect). The Rules view in the Inspector also lists selectors with the new positions within the edited stylesheet.
Differential Revision: https://phabricator.services.mozilla.com/D36585
--HG--
extra : moz-landing-system : lando
Bug 1451104 removed the GCC 4.9 toolchain, but left the build script and
the patch that only that toolchain build was using.
Differential Revision: https://phabricator.services.mozilla.com/D36886
--HG--
extra : moz-landing-system : lando
Changes:
- disable some tests in `toolkit/content/tests/chrome/chrome.ini` with approval from enndeakin
- migrate tests to run on macosx1014
Differential Revision: https://phabricator.services.mozilla.com/D36985
--HG--
extra : moz-landing-system : lando
Changes:
- remove `fail-if` conditions for tests that now pass on macosx1014
- add one `fail-if` condition for macosx1014 (`test_2_conformance2__textures__misc__tex-base-level-bug.html`) with approval from jgilbert
- migrate mochitest-webgl2-core test to run on macosx1014
Differential Revision: https://phabricator.services.mozilla.com/D36982
--HG--
extra : moz-landing-system : lando
Changes:
- tying up loose ends from D34589 where I forgot to remove mochitest-plain from macosx1010
Differential Revision: https://phabricator.services.mozilla.com/D36983
--HG--
extra : moz-landing-system : lando
When building Gecko/Android/aarch64 on Windows, `--target` parameter may not be incorrect value. Although `check_compiler`'s `info` is target compiler, clang on Windows is always detected as `clang-cl`, not `clang`.
```
c:/Users/mkato/.mozbuild/clang/bin/clang.exe -E -dM - < /dev/null
...
#define _MSC_VER 1916
```
So even if using clang on Windows, not clang-cl, we should detect as 'clang' correctly
Differential Revision: https://phabricator.services.mozilla.com/D36422
--HG--
extra : moz-landing-system : lando
