4dfe93e7c0811d6c130e4e56c967909fec494b03: Bug 1410714 - Help mach tests find adb when running Android tests; r=jmaher
Geoff Brown <gbrown@mozilla.com> - Tue, 24 Oct 2017 15:17:25 -0600 - rev 388068
Push 32740 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:30:59 +0000
Bug 1410714 - Help mach tests find adb when running Android tests; r=jmaher
00bec72d17c4591f10e7dc7930637a2dded95975: Bug 1405141 - Add stability checking to wptrunner, r=gbrown
James Graham <james@hoppipolla.co.uk> - Mon, 16 Oct 2017 14:33:41 +0100 - rev 388067
Push 32740 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:30:59 +0000
Bug 1405141 - Add stability checking to wptrunner, r=gbrown This adds a --verify flag that is compatible with other Mozilla test harnesses i.e. it runs each test 10 times without restarting and then runs it 5 times with restarts, and then repeats with chaos mode enabled. This uses the code from, and can replace, the |wpt run --stability| flag from upstream although that has different default behaviour (running 10 times with restarts). More work is needed to avoid duplicating all the code, however. MozReview-Commit-ID: 7oUEwJk7uhZ
0faad69400fac3a8cb9340e820380a5fca11d57f: Bug 1405141 - Add support for rerunning web-platform-tests without restarting, r=gbrown
James Graham <james@hoppipolla.co.uk> - Mon, 16 Oct 2017 14:32:27 +0100 - rev 388066
Push 32740 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:30:59 +0000
Bug 1405141 - Add support for rerunning web-platform-tests without restarting, r=gbrown This adds a --rerun=N flag which runs each selected test N times in a row. MozReview-Commit-ID: 4dGuPDkjWeZ
40e33c4b41fd68d572725d03705433a81a6b65ce: Bug 1410937 - Directly initialize result arrays in String.prototype.split specializations. r=jandem
André Bargull <andre.bargull@gmail.com> - Tue, 24 Oct 2017 01:05:50 +0900 - rev 388065
Push 32740 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:30:59 +0000
Bug 1410937 - Directly initialize result arrays in String.prototype.split specializations. r=jandem
1f17f122eb7c0a1a9d6f08bc55796c7ce8d954fe: Bug 1410640 - Enable nursery allocation of arrow functions. r=jonco
André Bargull <andre.bargull@gmail.com> - Tue, 24 Oct 2017 18:25:46 +0900 - rev 388064
Push 32740 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:30:59 +0000
Bug 1410640 - Enable nursery allocation of arrow functions. r=jonco
ec25214fbc5c67477c4e5a9edfd69215c9c3002e: Bug 1394196 - Update about:telemetry settings string to new data preference semantics. r=chutten
Georg Fritzsche <georg.fritzsche@googlemail.com> - Tue, 24 Oct 2017 04:47:00 -0400 - rev 388063
Push 32740 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:30:59 +0000
Bug 1394196 - Update about:telemetry settings string to new data preference semantics. r=chutten
252a8528c5ab4affc2742e7ccfe4ef4aa5ee42f8: Bug 1408811 followup 2 - Swap the annotation of empty-1.xul.
Xidorn Quan <me@upsuper.org> - Wed, 25 Oct 2017 14:47:11 +1100 - rev 388062
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1408811 followup 2 - Swap the annotation of empty-1.xul. MozReview-Commit-ID: 70FJ2D8HrAY
f6f6cee6c445fcef05b01b305caf3f716bff6918: Bug 1410771 - extend adaptive playback blacklist for some Samsung tablet. r=JamesCheng
John Lin <jolin@mozilla.com> - Wed, 25 Oct 2017 09:00:58 +0800 - rev 388061
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1410771 - extend adaptive playback blacklist for some Samsung tablet. r=JamesCheng MozReview-Commit-ID: 9X316WYjIS3
297434b40ea359a53a735396c1b8854480a5b3ff: servo: Merge #19009 - Update WR (clip alpha mul, pre-mul rects, box shadow fixes) (from glennw:update-wr-pre); r=jdm
Glenn Watson <github@intuitionlibrary.com> - Tue, 24 Oct 2017 20:20:37 -0500 - rev 388060
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
servo: Merge #19009 - Update WR (clip alpha mul, pre-mul rects, box shadow fixes) (from glennw:update-wr-pre); r=jdm Source-Repo: https://github.com/servo/servo Source-Revision: a65253a11aea13bb7cf26aabdcbac41c02d36f68
188ff8b2f7f6d7336bc830ff805b1d3e84ee9901: Bug 1407631 - Wait about 10 minutes after browser session start before scanning for unsubmitted crash reports. r=gsvelto
Mike Conley <mconley@mozilla.com> - Tue, 24 Oct 2017 16:55:24 -0400 - rev 388059
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1407631 - Wait about 10 minutes after browser session start before scanning for unsubmitted crash reports. r=gsvelto While the crash reporter client is submitting a crash report, the report itself stays in the crashes directory. We suspect that in some cases, if the browser starts up while the crash reporter client is still sending the report, the unsubmitted crash report handler will also attempt to send the same report. This patch makes the unsubmitted crash report handler wait approximately 10 minutes after the session starts before doing the unsubmitted crash report scan. MozReview-Commit-ID: KkrPDa1Qwv1
edc52ff233c42294140b0e22381f7f37cd30c345: Bug 1405359 - Add some logging code in ScrollingLayersHelper. r=jrmuizel
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Oct 2017 18:47:24 -0400 - rev 388058
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1405359 - Add some logging code in ScrollingLayersHelper. r=jrmuizel MozReview-Commit-ID: Lb4UeUxO5HL
d3d823602aa14b79688f969fca7f1b5514b479b8: Bug 1405359 - Avoid pushing and popping identical clip stacks for adjacent display items. r=jrmuizel
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Oct 2017 18:47:17 -0400 - rev 388057
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1405359 - Avoid pushing and popping identical clip stacks for adjacent display items. r=jrmuizel Instead of unconditionally pushing and popping clips per display item, this patch changes things so that for each recursive display list, we create an ItemClips struct. We push this onto the stack when we enter the display list, and pop it off at the end. For each display item, we check to see if the clips would actually change compared to the previous display item, and only do the pop/repush in that case. MozReview-Commit-ID: J0MCc2V9hWT
2cbf78901a3d029fc683e1ec6d00065820a902b7: Bug 1405359 - Make ScrollingLayersHelper a more stateful class. r=jrmuizel
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Oct 2017 18:46:44 -0400 - rev 388056
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1405359 - Make ScrollingLayersHelper a more stateful class. r=jrmuizel This makes ScrollingLayersHelper a non-RAII type class, and instead adds methods to notify it of when we start processing a new transaction or a new display item within the transaction. This patch has no functional changes, it's non-obvious refactoring. MozReview-Commit-ID: GEZzCGbVqB1
1921d545ea3933100baae89600c18b2209f8a434: Bug 1405359 - Replace the mPushed* variables with a more encapsulated struct. r=jrmuizel
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Oct 2017 18:45:28 -0400 - rev 388055
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1405359 - Replace the mPushed* variables with a more encapsulated struct. r=jrmuizel Storing the per-item clip state in a struct like this will allow us to easily compare the desired clip state across items, so we can avoid doing unnecessary work when going from one item to the next. This patch has no functional changes, it's just refactoring. MozReview-Commit-ID: GX2FX4YDusO
1345767fb2d502a9ab705ca73ccecbc7f5209c99: Bug 1405359 - Stop passing around the clip id cache in all the functions. r=jrmuizel
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Oct 2017 18:45:04 -0400 - rev 388054
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1405359 - Stop passing around the clip id cache in all the functions. r=jrmuizel Instead just keep a ref to it as a member variable. No functional change. MozReview-Commit-ID: 9jSBdZRIGuV
aaa39a5309985d35debb0aaeaa3316dc074aa608: Bug 1410107 - Grow audioipc server slabs as required. r=kinetik
Dan Glastonbury <dan.glastonbury@gmail.com> - Wed, 25 Oct 2017 09:14:45 +1000 - rev 388053
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1410107 - Grow audioipc server slabs as required. r=kinetik MozReview-Commit-ID: zFfex3LX7K
3170d21cbd25d32466502d12119f6d9824c84bbf: servo: Merge #19011 - Use actual size for old allocation in ft_realloc (from mbrubeck:realloc); r=glennw
Matt Brubeck <mbrubeck@limpet.net> - Tue, 24 Oct 2017 18:40:20 -0500 - rev 388052
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
servo: Merge #19011 - Use actual size for old allocation in ft_realloc (from mbrubeck:realloc); r=glennw Prevents crashes from improperly freed memory. Fixes #19008, fixes #18950, fixes #18949. - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #19008. - [x] There are tests for these changes Source-Repo: https://github.com/servo/servo Source-Revision: e1dac69a4054f208accd18aa443cae19ec7eaf53
680d798e440b9492e0409c01a40d85f6022fe09a: Bug 849593 - Skip samples of active SMIL timed elements when the sample time precedes the current interval; r=dholbert
Brian Birtles <birtles@gmail.com> - Tue, 24 Oct 2017 13:06:04 +0900 - rev 388051
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 849593 - Skip samples of active SMIL timed elements when the sample time precedes the current interval; r=dholbert In some circumstances it is possible to sample a timed element in the active state with a time that precedes is current interval. One possible sequence of steps leading to this situation is as follows: 1. A timed element (e.g. <set>, <animate>) with a non-zero begin time is the child of <svg> element A (its "time container") but has yet to be sampled. 2. In order to resolve its initial interval, the timed element registers a startup milestone with its time container at time 0. 3. However, before the sample is performed where the timed element's initial current interval is resolved, <svg> element A is detached from the document tree. 4. The timed element is then attached to a different <svg> element B that has a current time greater than the begin time of the timed element and less than that of <svg> element A. 5. Since the timed element is still in its startup state it registers its startup milestone again, this time with its new time container, i.e. <svg> element B. 6. A tick occurs or the document has its style flushed such that a sample is performed. This includes running the milestone sample which causes the timed element to resolve its initial current interval. Furthermore the subsequent regular sample of the timed element causes it to transition into its active state because the current time of <svg> element B is greater than the begin time of the timed element. 7. <svg> element A is re-attached to the document. 8. When we go to run the next sample, we iterate through all time containers associated with the document's animation controller which includes both <svg> element A, and <svg> element B. 9. <svg> element A renders up its 0 milestone from step (2) since it has yet to run it. It converts this to parent time, i.e. the time space of the animation controller, which will be zero or less depending on the current time of <svg> element A when it was re-attached. 10. Since the milestone from <svg> element A will be the earliest milestone time, it will be used as the next milestone sample time. 11. The timed element is then sampled using this time, but first it is converted to a time in the time space of the timed element's time container, which is now <svg> element B. As a result of this conversion, the sample time may end up being *before* the beginning of the timed element's current interval. Since timed elements never expect the time to go backwards an assertion fails when it detects that it is active, but is being sampled before its current interval. For this particular case, ignoring the "early" sample seems to be the most appropriate action. More generally, however, we can anticipate other cases similar to this where milestones are registered that cause the sample time to temporarily go backwards. A quick audit of nsSMILTimedElement::DoSampleAt suggests that, with the code changes from this patch, that is probably ok. As an alternative we could, perhaps, try to drop and re-create all milestones when time containers are re-attached to the document tree but that would add more complexity and would not necessarily cover other similar cases of this situation. I have verified that the crashtest included in this changeset fails without the code changes also in this changeset. MozReview-Commit-ID: KKGYRayNkpo
d22b8c27e4ccfcad474213c6d9789a29aa52ca4b: Bug 1408811 followup - Disable empty-1.xul for stylo windows.
Xidorn Quan <me@upsuper.org> - Wed, 25 Oct 2017 11:01:50 +1100 - rev 388050
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
Bug 1408811 followup - Disable empty-1.xul for stylo windows. MozReview-Commit-ID: Cx6rhArQm2j
718c237332ba9f7372f91ea233915ffcb3e7e486: servo: Merge #18981 - Merge request type and destination (from KiChjang:fold-type-destination); r=avadacatavra
Keith Yeung <kungfukeith11@gmail.com> - Tue, 24 Oct 2017 17:02:18 -0500 - rev 388049
Push 32739 by acraciun@mozilla.com at Wed, 25 Oct 2017 09:29:21 +0000
servo: Merge #18981 - Merge request type and destination (from KiChjang:fold-type-destination); r=avadacatavra Fixes #18278. Source-Repo: https://github.com/servo/servo Source-Revision: dcd7d2fa32aa53628a9be63a2d0ea64796cd968e
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip