bug 1505652: [taskgraph] Download debian packages from latest run of package task; r=dustin If a packaging task ended up being retried for any reason, the downstream docker tasks that depended on them would fail, since they were hard-coding the artifacts from the initial run. Differential Revision: https://phabricator.services.mozilla.com/D7364

Bug 1488515 - avoid wasm hardfp -> softfp transition twice on Android. r=bbouvier The baseline compiler should always call builtins assuming the hardfp calling convention on ARM, but it would actually take the native calling convention on the device into account and sometimes use the softfp convention. The reason the baseline compiler should always use hardfp is that the builtin thunks already convert hardfp->softfp along the call path and softfp->hardfp along the return path, if this is necessary, to allow wasm to call builtins using the hardfp convention always. It is possible that the situation was different when the baseline compiler was written and that the bug is the result of subsequent changes to the thunk layer, but this is not known precisely. There's a driveby fix here to simplify the logic around determining hardfp vs softfp for the system ABI; UseHardFpABI() is now always available and does the right thing, we don't need the #ifdef nest we had previously.

Backed out 6 changesets (bug 1504906 and bug 1505652) to give time to toolchains and docker images to build without blocking other landings. Backed out changeset 2fe1e2b7d9c6 (bug 1504906) Backed out changeset 27b4002951a4 (bug 1504906) Backed out changeset f7a685b16579 (bug 1504906) Backed out changeset f8064dbb8009 (bug 1504906) Backed out changeset f899fbb4a5d7 (bug 1504906) Backed out changeset 3f71db4aef73 (bug 1505652)

Bug 1504906 - Install the Gtk+ 3.10 packages and required dependencies in the build docker images. r=gps Interestingly, the resulting binaries are still compatible with Gtk+ 3.4. The only difference in symbol use are: g_log -> g_logv g_assertion_message -> g_assertion_message_expr Both of those symbols are actually available in older versions of glib. Some #defines just switched from using the latter rather than the former. Differential Revision: https://phabricator.services.mozilla.com/D11141

Bug 1504906 - Build 32-bits Gtk+ 3.10 packages for Debian Wheezy. r=gps This creates 32-bits variants of the same packages that were added for 64-bits builds, with a few additions: - python-defaults, so that the python package can be installed as a dependency of the libglib2.0-dev package, - xkeyboard-config, so that the xkb-data package can be installed as a dependency of the libxkbcommon0 package. Additionally, because the 32-bits and 64-bits packages are built separately (the 32-bits packages can't, on Wheezy, be built on a 64-bits host), they don't end up with the same changelog.Debian/changelog.Debian.gz file because of a timestamp within it. One way to address this would be to make the taskgraph more complex, by adding a task creating the source package, and then two tasks building the 32-bits and 64-bits binary packages from that source, but that's not worth the overhead, when a simple hack works around the problem: We make dpkg skip installing the changelog.Debian* files. Differential Revision: https://phabricator.services.mozilla.com/D11140

Bug 1504906 - Build 64-bits Gtk+ 3.10 packages for Debian Wheezy. r=gps Along with all the updated dependencies that are necessary to achieve this. Differential Revision: https://phabricator.services.mozilla.com/D11138

Bug 1504906 - Use a separate docker image for base toolchain builds. r=gps We're going to bump our shipped builds to build against Gtk+ 3.10, but still want to ensure we can still build against Gtk+ 3.4. As we're using Gtk+ packages installed in the build docker image, we need to have a separate image where the Gtk+ packages are kept at version 3.4. Differential Revision: https://phabricator.services.mozilla.com/D11137

Bug 1504906 - Add another -Werror exception for G_DEFINE_TYPE_EXTENDED. r=gps Versions of glib newer than the one we currently use adds a function we don't use. Differential Revision: https://phabricator.services.mozilla.com/D11136

bug 1505652: [taskgraph] Download debian packages from latest run of package task; r=dustin If a packaging task ended up being retried for any reason, the downstream docker tasks that depended on them would fail, since they were hard-coding the artifacts from the initial run. Differential Revision: https://phabricator.services.mozilla.com/D7364

bug 1492499: webdriver: disable maximize_window/stress.py on windows; a=stefan_hindli r=jgraham The Maximize Window command's stress test is broken on Windows due to a socket problem on Windows specifically. I think the problem is that the socket buffer is too small because of a very intensive check for the window size not changing. See https://bugzilla.mozilla.org/show_bug.cgi?id=1505806 for more details. Differential Revision: https://phabricator.services.mozilla.com/D11331

Bug 1460914 - [xpcshell] Add --setpref to the command line, r=ted Depends on D9796 Differential Revision: https://phabricator.services.mozilla.com/D9797

Bug 1460914 - [mozprofile] Move mochitest's 'parseKeyValue' function into mozprofile.cli, r=ted Parsing prefs and env on the command line is a common task performed by our harnesses, let's move it into mozbase. Depends on D9717 Differential Revision: https://phabricator.services.mozilla.com/D9796

Bug 1505544 - Update webrender to commit 6e445b0422075f66be4a2009745cad3fefe3429f (WR PR #3267). r=kats Differential Revision: https://phabricator.services.mozilla.com/D11323

No Bug, mozilla-central repo-update HSTS HPKP blocklist remote-settings tld-suffixes - a=repo-update r=RyanVM Differential Revision: https://phabricator.services.mozilla.com/D11314

Bug 1505213 - Allow ::slotted()::placeholder. r=heycam Differential Revision: https://phabricator.services.mozilla.com/D11132

bug 1505752 - fix whitespace trim of Timing-Allow-Origin header value r=dragana StripWhitespace() is not suitable for HTTP whitespace trimming. Differential Revision: https://phabricator.services.mozilla.com/D11317

bug 1492499: marionette: increase TimedPromise timeout on debug; r=whimboo The things that rely on TimedPromise, such as awaiting a sizemodechange event on exiting fullscreen, takes a lot longer to perform in Asan and debug builds than in optimised builds. This patch increases the TimedPromise timeout duration by three times in debug builds, which is the same amount WPT uses. Depends on D10569 Differential Revision: https://phabricator.services.mozilla.com/D11189

bug 1492499: marionette: drop broken window maximization test; r=automatedtester This test is duplicated by WPT tests. Depends on D10568 Differential Revision: https://phabricator.services.mozilla.com/D10569

bug 1492499: marionette: restore from maximized before setting rect; r=whimboo On certain window manager configurations a window may be resized to fit the full available dimensions of the screen without going into the maximised state. Similarily, a maximised window may be the exact dimensions of the screen. If the window outerWidth/outerHeight is 800x600 and in maximised state, resizing it to 800x600 through WebDriver:SetWindowRect will not work because the window has already reached its requested dimensions. This patch ensures to wait for the resizeEnd event when the window state is not normal. Depends on D8419 Differential Revision: https://phabricator.services.mozilla.com/D10568

bug 1492499: marionette: empty event queue on window manipulation; r=automatedtester,whimboo This requests an animation frame off ChromeWindow and waits for the main thread's event queue to become idle in relation to window manipulation commands. It additionally clears the event queue before resizing, because this is a particularly hazardous operation. We don't know the exact science as to why this is needed, so it may just be that this introduces enough latency for the operation to complete successfully. File this under "secret sauce". This ensures all potential synchronisation code between e.g. the parent process and the child processes have had time to run before we return from WebDriver:{MinimizeWindow,MaximizeWindow,FullscreenWindow}. Depends on D8418 Differential Revision: https://phabricator.services.mozilla.com/D8419