072bf0d7270d25d4892967402c0a1c5eebe0bf9b: bug 1505652: [taskgraph] Download debian packages from latest run of package task; r=dustin
Tom Prince <mozilla@hocat.ca> - Tue, 02 Oct 2018 21:38:23 +0000 - rev 501588
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
f9108997903c74814e3f3b4d8d9548bcbf9e7149: Bug 1488515 - avoid wasm hardfp -> softfp transition twice on Android. r=bbouvier
Lars T Hansen <lhansen@mozilla.com> - Wed, 07 Nov 2018 15:12:56 +0100 - rev 501587
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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.
5ece74940a5f39b5c2840400ed05112ebf1eaa15: Backed out 6 changesets (bug 1504906 and bug 1505652) to give time to toolchains and docker images to build without blocking other landings.
Mike Hommey <mh+mozilla@glandium.org> - Thu, 08 Nov 2018 17:14:16 +0900 - rev 501586
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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)
2fe1e2b7d9c63f3f29e3b4b33412b233ae779ce4: Bug 1504906 - Install the Gtk+ 3.10 packages and required dependencies in the build docker images. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 07 Nov 2018 09:52:39 +0900 - rev 501585
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
27b4002951a4e763eca65972c6fb2432bc21a3dd: Bug 1504906 - Build 32-bits Gtk+ 3.10 packages for Debian Wheezy. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 07 Nov 2018 09:20:50 +0900 - rev 501584
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
f7a685b165798f63cefe7293f0a2e53f7afa0e4a: Bug 1504906 - Build 64-bits Gtk+ 3.10 packages for Debian Wheezy. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 07 Nov 2018 08:55:45 +0900 - rev 501583
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
f8064dbb80097ad6a8131d790c25169ae4e5520e: Bug 1504906 - Use a separate docker image for base toolchain builds. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 07 Nov 2018 08:52:51 +0900 - rev 501582
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
f899fbb4a5d7e0b604af4081d46d7d3e68f42674: Bug 1504906 - Add another -Werror exception for G_DEFINE_TYPE_EXTENDED. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Wed, 07 Nov 2018 08:51:11 +0900 - rev 501581
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
3f71db4aef7361659bd324dd6a9c29933fddf32e: bug 1505652: [taskgraph] Download debian packages from latest run of package task; r=dustin
Tom Prince <mozilla@hocat.ca> - Tue, 02 Oct 2018 21:38:23 +0000 - rev 501580
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
c812e3810b9451c4080a39c6d0fa1c06dfad7d7e: bug 1492499: webdriver: disable maximize_window/stress.py on windows; a=stefan_hindli r=jgraham
Andreas Tolfsen <ato@sny.no> - Thu, 08 Nov 2018 15:38:15 +0000 - rev 501579
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
531299c96e09053ef5451fd67453f6147f5a6e99: Bug 1460914 - [xpcshell] Add --setpref to the command line, r=ted
Andrew Halberstadt <ahalberstadt@mozilla.com> - Thu, 08 Nov 2018 14:50:32 +0000 - rev 501578
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1460914 - [xpcshell] Add --setpref to the command line, r=ted Depends on D9796 Differential Revision: https://phabricator.services.mozilla.com/D9797
f99b45112279bbf314dba4224fc0bf19ac2cd1ca: Bug 1460914 - [mozprofile] Move mochitest's 'parseKeyValue' function into mozprofile.cli, r=ted
Andrew Halberstadt <ahalberstadt@mozilla.com> - Thu, 08 Nov 2018 14:51:26 +0000 - rev 501577
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
2a1f9baafbecd28da55d87844692a6f745b728d8: Bug 1505544 - Update webrender to commit 6e445b0422075f66be4a2009745cad3fefe3429f (WR PR #3267). r=kats
WR Updater Bot <graphics-team@mozilla.staktrace.com> - Thu, 08 Nov 2018 14:25:30 +0000 - rev 501576
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1505544 - Update webrender to commit 6e445b0422075f66be4a2009745cad3fefe3429f (WR PR #3267). r=kats Differential Revision: https://phabricator.services.mozilla.com/D11323
5ed738467221b4be29f252c8588e5a645af124bf: No Bug, mozilla-central repo-update HSTS HPKP blocklist remote-settings tld-suffixes - a=repo-update r=RyanVM
ffxbld <ffxbld@mozilla.com> - Thu, 08 Nov 2018 13:54:03 +0000 - rev 501575
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
8735038d615f99a6a9fe4fa44d26be3b6b6bb727: Bug 1505213 - Allow ::slotted()::placeholder. r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 08 Nov 2018 13:33:59 +0000 - rev 501574
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1505213 - Allow ::slotted()::placeholder. r=heycam Differential Revision: https://phabricator.services.mozilla.com/D11132
c359697043078fa233fd45d044263fe6db5eeb3d: bug 1505752 - fix whitespace trim of Timing-Allow-Origin header value r=dragana
Daniel Stenberg <daniel@haxx.se> - Thu, 08 Nov 2018 13:14:43 +0000 - rev 501573
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
2c1b00a6a97f90dea740c046759698bed3a4c6fe: bug 1492499: marionette: increase TimedPromise timeout on debug; r=whimboo
Andreas Tolfsen <ato@sny.no> - Thu, 08 Nov 2018 13:11:40 +0000 - rev 501572
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
a4fcddffde4140fc2c0597055ae216eed4c795fd: bug 1492499: marionette: drop broken window maximization test; r=automatedtester
Andreas Tolfsen <ato@sny.no> - Thu, 08 Nov 2018 13:11:38 +0000 - rev 501571
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
81ac8f7d11b1d003d1a64ad94bfef4cb49553f91: bug 1492499: marionette: restore from maximized before setting rect; r=whimboo
Andreas Tolfsen <ato@sny.no> - Thu, 08 Nov 2018 13:11:31 +0000 - rev 501570
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
05b349eaba5481fc81f443be601e612303abe85b: bug 1492499: marionette: empty event queue on window manipulation; r=automatedtester,whimboo
Andreas Tolfsen <ato@sny.no> - Thu, 08 Nov 2018 13:11:28 +0000 - rev 501569
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
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
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip