34fc2ff698c3796600e79073daa6011f24aecc06: Bug 1435319 - tests, r=valentin
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Tue, 19 Jun 2018 12:11:34 +0100 - rev 423133
Push
34164 by csabou@mozilla.com at Thu, 21 Jun 2018 01:17:13 +0000
Bug 1435319 - tests, r=valentin
b58c103b639f29520c952137cd607148e2b01675: Bug 1435319, r=valentin
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Wed, 13 Jun 2018 08:15:40 -0700 - rev 423132
Push
34164 by csabou@mozilla.com at Thu, 21 Jun 2018 01:17:13 +0000
1d069afa41fa40ba8c5835dbd83f1218c46b83e7: Bug 1461948 - Uncouple ReferenceType from TypedObject's ReferenceTypeDescr. r=till
Lars T Hansen <lhansen@mozilla.com> - Wed, 16 May 2018 13:44:40 +0200 - rev 423131
Push
34164 by csabou@mozilla.com at Thu, 21 Jun 2018 01:17:13 +0000
Bug 1461948 - Uncouple ReferenceType from TypedObject's ReferenceTypeDescr. r=till
The coupling created some problems for a later patch where I need to
reference ReferenceTypeDescr::Type in GlobalObject.h, but can't,
because this creates a circular include path. As for SIMD and Scalar,
there's no reason to embed the type all the way inside the TypedObject
machinery, we can just have it as its own thing.
c8434494445c6b5403c292226498a78b3d428331: Bug 1461948 - Generalize and abstract TypedObject field layout algorithm. r=till
Lars T Hansen <lhansen@mozilla.com> - Wed, 16 May 2018 09:44:14 +0200 - rev 423130
Push
34164 by csabou@mozilla.com at Thu, 21 Jun 2018 01:17:13 +0000
Bug 1461948 - Generalize and abstract TypedObject field layout algorithm. r=till
The algorithm is used by code that builds the TypeDesc, but also
needed earlier by the Wasm parser to build the compilation
environment. So abstract the algorithm and expose it.
e6cd4f48162d22ef3608391bbf16e7509e39de11: Bug 1461948 - Factor the TypedObject struct type constructor. r=till
Lars T Hansen <lhansen@mozilla.com> - Tue, 15 May 2018 19:49:44 +0200 - rev 423129
Push
34164 by csabou@mozilla.com at Thu, 21 Jun 2018 01:17:13 +0000
Bug 1461948 - Factor the TypedObject struct type constructor. r=till
For Wasm support we'll want to bypass the bits that interpret the
object coming from JS, and instead just pass in parallel arrays of IDs
and type descriptors, and other parameters.
This also allows us to request an opaque type, even if none of the
field types are opaque.
85493d8b9dae872d8b594f145fc289fb49ab0a4e: Bug 1453795 - Widget/Cocoa - Initialize member fields in classes/ structures. r=mstange
Andi-Bogdan Postelnicu <bpostelnicu@mozilla.com> - Fri, 15 Jun 2018 17:15:23 +0300 - rev 423128
Push
34164 by csabou@mozilla.com at Thu, 21 Jun 2018 01:17:13 +0000
Bug 1453795 - Widget/Cocoa - Initialize member fields in classes/ structures. r=mstange
00ae61d464066c27a4485e5f0dae02a7b78243ac: Bug 1453795 - XPCOM - Initialize member fields in classes/ structures. r=froydnj
Andi-Bogdan Postelnicu <bpostelnicu@mozilla.com> - Fri, 15 Jun 2018 14:41:20 +0300 - rev 423127
Push
34164 by csabou@mozilla.com at Thu, 21 Jun 2018 01:17:13 +0000
Bug 1453795 - XPCOM - Initialize member fields in classes/ structures. r=froydnj
e7d6ae2adfe21485357b3254e05157f58766420d: Bug 1423017 followup - Make the telemetry opt-out on release channel.
Xidorn Quan <me@upsuper.org> - Wed, 20 Jun 2018 13:34:14 +1000 - rev 423126
Push
34164 by csabou@mozilla.com at Thu, 21 Jun 2018 01:17:13 +0000
Bug 1423017 followup - Make the telemetry opt-out on release channel.
e09fbaee1456a373382d2d5bf6ab7321e26e3710: bug 1470005 - change default TRR blacklist duration to 60 seconds r=mcmanus
Daniel Stenberg <daniel@haxx.se> - Wed, 20 Jun 2018 23:44:19 +0200 - rev 423125
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
bug 1470005 - change default TRR blacklist duration to 60 seconds r=mcmanus
MozReview-Commit-ID: FGQCmhlBBG8
d69617c50c04497f084bd5a39ee698dff4cb4282: Bug 1463917 part 2 - Have windows widget render scrollcorner. r=jimm
Xidorn Quan <me@upsuper.org> - Fri, 11 May 2018 10:21:22 +1000 - rev 423124
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1463917 part 2 - Have windows widget render scrollcorner. r=jimm
MozReview-Commit-ID: K4Cu1mL6xvH
d1321b14461680936a84f7a283e55cb4085b0d61: Bug 1463917 part 1 - Add scrollcorner to -moz-appearance so that widget can render it. r=heycam
Xidorn Quan <me@upsuper.org> - Fri, 11 May 2018 10:12:17 +1000 - rev 423123
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1463917 part 1 - Add scrollcorner to -moz-appearance so that widget can render it. r=heycam
MozReview-Commit-ID: 1Za22ifONfG
88a05771dd2bfbd22e31a543c7403414886e1523: Bug 1469095 - Fix always-optimized jobs after bug 1465181. r=dustin
Mike Hommey <mh+mozilla@glandium.org> - Sat, 16 Jun 2018 10:15:50 +0900 - rev 423122
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1469095 - Fix always-optimized jobs after
bug 1465181. r=dustin
08b8d3da8635e10564150b04742b787d74d372e6: bug 1463356 do not count "not started" TRR resolves as failures r=mcmanus
Daniel Stenberg <daniel@haxx.se> - Wed, 20 Jun 2018 11:00:19 +0200 - rev 423121
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
bug 1463356 do not count "not started" TRR resolves as failures r=mcmanus
... when comparing against the native resolver. DNS_TRR_COMPARE is meant
to compare how the actually performed name resolves fare against each
other.
MozReview-Commit-ID: 98NoUGPpHr6
ddde6ad6d9e6c4069632e195613bcd53a39883e4: Bug 1469257 - [H264] Only check for SPS changes on keyframe r=bryce
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 20 Jun 2018 19:24:34 +0000 - rev 423120
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1469257 - [H264] Only check for SPS changes on keyframe r=bryce
Some invalid streams contain SPS changes and those appear to only occur on non-keyframe, this cause all frames to be dropped until the next keyframe is found. This result in apparent freezes.
While it is theoretically possible to have SPS changes inband on non-keyframe those should be very rare (I've never seen one). The content would have been invalid anyway in an non-fragmented mp4.
So we now only check for a SPS change on keyframe. This would cause no affect on either windows, android or ffmpeg as those decoders handle format change fine. The mac decoder could however show garbled frames temporarily.
Differential Revision:
https://phabricator.services.mozilla.com/D1733
3c53e83acb19a4e319758b1c8f19f2107732c1df: Bug 1465253: use postfix as prefix when logging and log in clear. r=bwc
Nils Ohlmeier [:drno] <drno@ohlmeier.org> - Mon, 07 May 2018 13:30:00 -0700 - rev 423119
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1465253: use postfix as prefix when logging and log in clear. r=bwc
MozReview-Commit-ID: 4bfVQZyM9qy
7b5b59d44cead15900cdc4e79c7657cc11be5349: Bug 1466379 - fall back to currentURI in case images are blocked, r=bz,dao
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Thu, 07 Jun 2018 16:20:29 +0100 - rev 423118
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1466379 - fall back to currentURI in case images are blocked, r=bz,dao
MozReview-Commit-ID: FW2f18pF4t5
11018f20ca8dbeef5e71a4a67882d9b51ee90c03: Bug 1469766 - Update OOM hook on rustc 1.28 after rust PR 51543. r=froydnj
Mike Hommey <mh+mozilla@glandium.org> - Wed, 20 Jun 2018 13:44:10 +0900 - rev 423117
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1469766 - Update OOM hook on rustc 1.28 after rust PR 51543. r=froydnj
5cc046f4654100da7d01a0e44aa069331860f784: Bug 1469676 - Reduce max-run-time for various build tasks; r=glandium
Gregory Szorc <gps@mozilla.com> - Wed, 20 Jun 2018 20:59:01 +0000 - rev 423116
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1469676 - Reduce max-run-time for various build tasks; r=glandium
The max-run-time for tasks appears to have been mostly cargo
culted. In particular, a value of 36000 (10 hours) is quite absurd:
no single task takes that long to execute.
This commit reduces the max-run-time of several tasks to
more reasonable values. The goal here is to prevent
excessively long-running tasks. There is definitely room to
further tweak values to further mitigate long-running tasks. But
let's bite off the biggest chunk first, since that doesn't
require much mental effort.
There is a possibility I overshot on some of these tasks. If we
get timeouts, we can always increase the timeout again.
Differential Revision:
https://phabricator.services.mozilla.com/D1716
c9487350a119359a14bce87083e34930ba6258df: Bug 1469683 - 3. Make sure cached session is closed after crash; r=esawin
Jim Chen <nchen@mozilla.com> - Wed, 20 Jun 2018 16:46:21 -0400 - rev 423115
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1469683 - 3. Make sure cached session is closed after crash; r=esawin
If @IgnoreCrash is specified, assume there has been a crash and
therefore wait for the cached session to close at the end of the test,
so that the closing operation doesn't carry over to the next test.
MozReview-Commit-ID: KrMfHgIiELQ
13ff68c7707d414ea98096933b322025a75ad871: Bug 1469683 - 2. Make child crashes throw special exception; r=esawin
Jim Chen <nchen@mozilla.com> - Wed, 20 Jun 2018 16:46:21 -0400 - rev 423114
Push
34163 by csabou@mozilla.com at Thu, 21 Jun 2018 01:14:46 +0000
Bug 1469683 - 2. Make child crashes throw special exception; r=esawin
Make child crashes throw ChildCrashException instead of the generic
RuntimeException, which can mean a variety of errors such as timeout.
MozReview-Commit-ID: H0E6gipkTxg