When installing JDK 1.8, it writes path to the following registry.
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.8\JavaHome
So we use this registry to detect JDK installation path on Windows if available.
Differential Revision: https://phabricator.services.mozilla.com/D20449
--HG--
extra : rebase_source : d8a380d9839f4de749815f3c81665e8d00226862
Since Windows doesn't call mach command from MSYS shell, we need python path
to call mach.
Differential Revision: https://phabricator.services.mozilla.com/D20448
--HG--
extra : rebase_source : 94752c75c7c56e3f33765e86d3e4335557b59223
Even though we don't look at the chrome value on android in nsLayoutUtils::AreRetainedDisplayListsEnabled(), I flipped it just in case someone looks at that pref somewhere else.
Depends on D25280
Differential Revision: https://phabricator.services.mozilla.com/D25281
--HG--
extra : moz-landing-system : lando
All three failures are small antialiasing differences in the text in the test. The text in the tests aren't even testing anything, they just describe what to expect from the test.
Until we get fuzzy matching in web platform tests (bug 1478472) we just have to mark them as fails, but we can be very specific about the platform, so we're probably still passing these tests on other android jobs if they are run there (not sure).
Differential Revision: https://phabricator.services.mozilla.com/D25280
--HG--
extra : moz-landing-system : lando
Add missing MOZ_SANDBOX preprocessor check before including Sandbox.h to fix the code coverage build.
Remove unused nsMacUtilsImpl.h #include.
Differential Revision: https://phabricator.services.mozilla.com/D25287
--HG--
extra : moz-landing-system : lando
I agree that we should remove PostCSS but since we have contributors moving to MC, I want to get this fixed ASAP.
Differential Revision: https://phabricator.services.mozilla.com/D25258
--HG--
extra : moz-landing-system : lando
Removes Node.js as an option for library detection to prevent issues in console.
Differential Revision: https://phabricator.services.mozilla.com/D25236
--HG--
extra : moz-landing-system : lando
Skip mochitest-chrome test failing frequently on android/pgo. This directory of tests
only runs on Android 4.3, so the manifest annotation is simple.
Discussed in bug; see comment 17.
Differential Revision: https://phabricator.services.mozilla.com/D25274
--HG--
extra : moz-landing-system : lando
This was causing test failures in some uncommon try configurations like fuzzing.
Depends on D24208
Differential Revision: https://phabricator.services.mozilla.com/D25253
--HG--
extra : moz-landing-system : lando
To prevent new buffer object from being created per frame, either
Sample.CREATOR has to keep track of all buffers from every remote codec,
or the client must memorize seen buffers and avoid asking for them again
and again. The former saves client code from modifications but complicates
the implementation of Sample, a data structure class, while the latter
requires changes to client code but avoid overcomplicating Sample.CREATOR
implementation.
The 2nd approach is taken:
- move SampleBuffer out of Sample, and update clients accordingly
- add a new IPC method for clients to get the buffers only when needed
Differential Revision: https://phabricator.services.mozilla.com/D24590
--HG--
extra : moz-landing-system : lando