MozReview-Commit-ID: HB5p6Kt0zTb

Bug 1389021 - Force CompositorManagerParent to close before shutting down the compositor thread. r=dvander,me

MozReview-Commit-ID: GThhGRFgEld

--HG--
extra : amend_source : 59f7e14d32adbfa72f5de2beb04cf67722b9b8fa

MozReview-Commit-ID: 1CvdUz7Uti0

Backed out changesets ef813898b5d3, ce228388aaf6, and c798f482b2c5 (bug 1396098) for violating TC cache constraints

CLOSED TREE

--HG--
extra : amend_source : 84120d6bacb5d72a9fbe41e4c3b405d63825da7c
extra : histedit_source : 8320c2193761b745f10850055ee74a3c9ac73615%2Cfbc2a28d8c5004a53305ef858ca5aea4245691e0

Add a `window` parameter to all Prompt.jsm usages, so the prompt will
appear in the correct window. This includes HelperAppDialog.js, which
was preventing the download chooser dialog from appearing in a custom
tab window.

The patch also moves `getActiveDispatcher` from GeckoViewPermission to
GeckoViewUtils, and makes several improvements to `getChromeWindow` and
`getDispatcherForWindow`. Prompt.jsm now uses the active
WindowDispatcher in the fallback scenario where we don't have a window.

MozReview-Commit-ID: KpAFMCZzQZp

Now that we have a Docker image with newer library versions on it, we
can move our builds over.  The new images differ from the old
CentOS-based images in two important ways, though:

1) The system compilers in the new image are new enough to be used as
   host compilers; additionally, our CentOS-built GCC compilers will not
   work.  We need to change the Android mozconfigs to reflect that.  We
   also need to change the Android tasks to not depend on the GCC
   toolchain builds.

2) In a similar fashion, we can use the system JDK; we no longer need to
   use the JDK from the Android NDK, which we had packaged up via the
   Android dependencies task.

Both of these changes come with caveats: our l10n repack jobs continue
to run on the CentOS-based images; l10n repacks have not been completely
converted to Taskcluster.  So we need to:

1) Retain the use of our custom GCC toolchain for HOST_CC/HOST_CXX on
   the CentOS-based images.

2) Retain the JDK packages in the tooltool manifests, and referencing
   them when we build on the CentOS-based images.

This seems like the obvious thing to want to happen.

CentOS 6 is pinned to glibc 2.12, but newer Android build-tools (like
aapt) require glibc 2.14.  It's not possible to safely upgrade CentOS
6 distributions to glibc 2.14.

CentOS 7 is pinned to glibc 2.17, which is new enough for newer
Android build-tools. However, I had great difficulty bringing forward
our existing centos:6 Docker image to centos:7.  In particular,
installing recent enough Mercurial, git, Python, and pip versions was
difficult enough that I elected to not pursue this approach.

Instead, I've elected to follow glandium's suggestion from
https://bugzilla.mozilla.org/show_bug.cgi?id=1370119#c5: base on
Debian with snapshots.debian.org for reproducibility.

The most significant changes here:

- using Debian's snapshots repository
- using Python and related tools provided by Debian and baked into the
  build image
- using the JDK and JRE provided by Debian and baked into the build
  image, rather than versions from tooltool (or eventually a toolchain
  build)

Moving the builds over to use this image will follow in the patches
ahead.

The name `android-gradle-build` is an accident of history; let's rename it
before we attempt major surgery on it.

--HG--
rename : taskcluster/docker/android-gradle-build/Dockerfile => taskcluster/docker/android-build/Dockerfile
rename : taskcluster/docker/android-gradle-build/README.md => taskcluster/docker/android-build/README.md
rename : taskcluster/docker/android-gradle-build/REGISTRY => taskcluster/docker/android-build/REGISTRY
rename : taskcluster/docker/android-gradle-build/VERSION => taskcluster/docker/android-build/VERSION
rename : taskcluster/docker/android-gradle-build/buildprops.json => taskcluster/docker/android-build/buildprops.json
rename : taskcluster/docker/android-gradle-build/dot-config/pip/pip.conf => taskcluster/docker/android-build/dot-config/pip/pip.conf
rename : taskcluster/docker/android-gradle-build/oauth.txt => taskcluster/docker/android-build/oauth.txt

No sense doing unnecessary work.

MozReview-Commit-ID: JFvnANsTS0r

Parts of Spidermonkey expect the bytecode length to always be non-zero.
Bug 1399373 shows crashes when this assumption fails. This patch moves
the check closer to source of error.

MozReview-Commit-ID: 8JROF2KCrNx

MozReview-Commit-ID: JDSKZLgij83

Bug 1395697 - Do not generate bouncer entries for BZ2-compressed MAR files for beta and devedition. r=catlee

MozReview-Commit-ID: 5L1Tk1dnicT

Bug 1399100, enhance client.py to warn when a local patch is registered for nspr/nss, based on feedback from glandium, r=fkiefer

Bug 1399100, temporarily expose an NSPR helper function, only for Firefox 57, feedback+=mcmanus, r=fkiefer
This is an exception from the usual NSPR release upgrade process and essentially an agreed temporary fork, which will be undone for Firefox 58.
This change isn't causing any harm, because the temporary API is used only for Windows, and only accessed using dynamic symbol lookup, so it will not cause any issue on operating systems that use a system-wide install copy of NSPR without the symbol.
UPGRADE_NSPR_RELEASE

UPGRADE_NSPR_RELEASE

MozReview-Commit-ID: 1QFbWCThVeg

--HG--
rename : browser/extensions/screenshots/webextension/icons/onboarding-4.png => browser/extensions/screenshots/webextension/icons/onboarding-5.png
extra : transplant_source : 1%8AV%EBZ%A5%18%F9%BD%E9%EA%ADv%DEbm%BF%EF5N

Bug 1400473 - Update talos test tpaint.html to comply with new toplevel data: URI navigation policy. r=jmaher

Bug 1400347 - Update test_ext_tabs_captureVisibleTab.html to comply with new toplevel data: URI navigation policy. r=smaug

bug 1368652 - test that viewing a certificate with a long OID doesn't crash the browser r=Cykesiopka

MozReview-Commit-ID: JhUvDEJJvJy

--HG--
extra : rebase_source : 37046eb12c04f93e869c0a8b108bcf504ccaabae

Bug 1398514 - Disable browser/components/extensions/test/browser/test-oop-extensions/browser_ext_tabs_executeScript_runAt.js on windows for frequent failures. r=me, a=test-only

Bug 1389983 - Disable dom/media/tests/mochitest/test_getUserMedia_addtrack_removetrack_events.html on linux debug for frequent failures. r=me, a=test-only

Bug 1387673 - Disable /webrtc/RTCPeerConnection-setRemoteDescription-answer.html for frequent failures. r=me, a=test-only

Bug 1380968 - Disable browser/components/sessionstore/test/browser_522545.js for frequent failures. r=me, a=test-only

Bug 1370056 - Disable /XMLHttpRequest/send-response-event-order.htm on windows for frequent failures. r=me, a=test-only

Bug 1373347 - Disable /XMLHttpRequest/send-response-upload-event-progress.htm on windows for frequent failures. r=me, a=test-only

Bug 1282262 - Disable dom/media/tests/mochitest/test_getUserMedia_mediaStreamClone.html for frequent failures. r=me, a=test-only

CopySurface doesn't respect any existing clips that are applied to the draw
target. It doesn't look like nsNativeThemeGTK uses CopySurface normally, but
when OMTP is enabled the draw target is a DrawTargetCapture which can't
LockBits() which causes us to use CopySurface. This can cause a reftest failure.

MozReview-Commit-ID: 1mYMhQB0r3M

--HG--
extra : rebase_source : d2683dee37ce32049d8daeee786cbb06ba624438
extra : amend_source : 59c48b66f733108636d52047a55889ee0c4e2746