3cf260e1fb9ce549b29f9200b68e0e85f5e5ae0b: Bug 1405349 - [reftest] Refactor manifest parsing from reftest.jsm to standalone module, r=jmaher
Andrew Halberstadt <ahalberstadt@mozilla.com> - Mon, 02 Oct 2017 12:03:43 -0400 - rev 386088
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1405349 - [reftest] Refactor manifest parsing from reftest.jsm to standalone module, r=jmaher There are two motivations for this change. First, reftest.jsm has become very large and monolithic. It has lots of global state and is hard to modify without breaking something. This change is a first attempt at dividing reftest.jsm into multiple standalone(ish) modules. This will make it easier to comprehend and extend. Second, we'd like to implement "run-by-manifest" mode for reftest. This means we'll restart the browser between each manifest run. This means much of the state which is normally stored in global variables in reftest.jsm, will instead need to be stored in python. A prerequisite to doing that is parsing the manifests before starting the test suite. A prerequisite to that is moving the manifest parsing code into a standalone JSM. This is the first step. MozReview-Commit-ID: 42epTs8EU1O
c6a234f1453ee01002954b0f7b450945b7f0a3a3: Bug 1408368 - move aboutdevtools.dtd out of localized folder;r=nchevobbe,Pike
Julian Descottes <jdescottes@mozilla.com> - Fri, 13 Oct 2017 14:21:31 +0200 - rev 386087
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1408368 - move aboutdevtools.dtd out of localized folder;r=nchevobbe,Pike MozReview-Commit-ID: 6jHqNcqONh3
3e504c84f3d3755513c4518972574b7a282e097b: Bug 1393272 - Use original width and height if either the scaled width or height is 0. r=jya
Kilik Kuo <kikuo@mozilla.com> - Thu, 12 Oct 2017 16:40:50 +0800 - rev 386086
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1393272 - Use original width and height if either the scaled width or height is 0. r=jya MozReview-Commit-ID: 3y4c5zJZD0a
4c82578ae3107df850f23740f88e1b857657fbbb: Bug 1389094 - Increase height of sidebar search bar and tree items in touch mode. r=dao
Nihanth Subramanya <nhnt11@gmail.com> - Sun, 08 Oct 2017 22:06:30 +0530 - rev 386085
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1389094 - Increase height of sidebar search bar and tree items in touch mode. r=dao MozReview-Commit-ID: HxT3eNHImyz
56094e2f7e98daf1546c99ba26a3f40425d07c41: servo: Merge #18847 - style: Split the invalidation processing from the invalidator step (from emilio:invalidation-generic); r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 13 Oct 2017 06:14:42 -0500 - rev 386084
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
servo: Merge #18847 - style: Split the invalidation processing from the invalidator step (from emilio:invalidation-generic); r=heycam This is the first step in reusing the invalidation machinery for other stuff, potentially including QuerySelector / QuerySelectorAll. Source-Repo: https://github.com/servo/servo Source-Revision: a89a76e1fc138bd1a60ee974abfc47a4b0f69c09
e676d685201215b687fd5946712d5d457d6722dd: Bug 1407940 - P2. Only ever access mTaskQueue in a thread-safe fashion. r=alwu,gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 12 Oct 2017 13:30:47 +0200 - rev 386083
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1407940 - P2. Only ever access mTaskQueue in a thread-safe fashion. r=alwu,gerald mTaskQueue is only read on the main thread, but read and written on the demuxer's taskqueue. We need to ensure that accesses are synchronised. MozReview-Commit-ID: Gbc15iYgZOe
05efc1a5fb95401eae2454d7927c09e39dc5de03: Bug 1407940 - P1. Use Mutex in place of Monitor. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 12 Oct 2017 11:15:20 +0200 - rev 386082
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1407940 - P1. Use Mutex in place of Monitor. r=gerald MozReview-Commit-ID: Dy2WhS0YOq1
a39ec568715b5d1efb06198c4be3664de056a7fd: Bug 1408284 - Build sccache with gcc instead of clang. r=ted
Mike Hommey <mh+mozilla@glandium.org> - Fri, 13 Oct 2017 14:27:13 +0900 - rev 386081
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1408284 - Build sccache with gcc instead of clang. r=ted When adding sccache toolchain jobs in bug 1381772, building with gcc failed, and building with clang worked, so I just went with the path of least resistance. That's however a suboptimal position in the dependency graph, so it's still preferable to use gcc if possible. Looking exactly how it fails, it turns out it's because without CC being set, ring wants to build with "cc", which ends up being the system gcc instead of ours (our gcc archive doesn't provide "cc", only "gcc"), and it is too old to support the compiler flags ring uses. So setting CC does the trick.
d6394715adb74585c26ec27c91d7d70461fc2dda: Bug 1405584 - Add telemetry to track toolbox open time. r=francois,jdescottes datareview=francois
Alexandre Poirot <poirot.alex@gmail.com> - Wed, 11 Oct 2017 11:43:25 +0200 - rev 386080
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1405584 - Add telemetry to track toolbox open time. r=francois,jdescottes datareview=francois MozReview-Commit-ID: EuaYQBx8rbE
906745acb1ad4ab69116dfad1d2a19efe7568ad8: merge mozilla-central to autoland. r=merge a=merge
Sebastian Hengst <archaeopteryx@coole-files.de> - Fri, 13 Oct 2017 11:51:55 +0200 - rev 386079
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
merge mozilla-central to autoland. r=merge a=merge
50557e43a2086a7ac6950edb15c7ba53bb4b3bd8: servo: Merge #18861 - Some fixes to diagnostic hashmap (from upsuper:diagnose-fix); r=Manishearth
Xidorn Quan <me@upsuper.org> - Fri, 13 Oct 2017 02:11:55 -0500 - rev 386078
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
servo: Merge #18861 - Some fixes to diagnostic hashmap (from upsuper:diagnose-fix); r=Manishearth Source-Repo: https://github.com/servo/servo Source-Revision: ec00c660f0a1892033ca89a31d393427d3c6a2d3
885aeb78d65267247d3717c8e02e3364eaf3693a: Bug 1407968 - Add an exception for ESLint no-self-compare in test_complex_keyPaths.js as the comparisons are intentional. r=bevis
Mark Banner <standard8@mozilla.com> - Fri, 13 Oct 2017 09:47:17 +0100 - rev 386077
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1407968 - Add an exception for ESLint no-self-compare in test_complex_keyPaths.js as the comparisons are intentional. r=bevis MozReview-Commit-ID: 7rSKeU9qtja
84907247d8f56fd7c92a341e5c70c670fb78eaa1: Bug 1403910 - Enable and rename browser_webconsole_No_input_and_Tab_key_pressed.js on the new console frontend; r=Honza
Nicolas Chevobbe <nchevobbe@mozilla.com> - Thu, 12 Oct 2017 16:03:04 +0200 - rev 386076
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1403910 - Enable and rename browser_webconsole_No_input_and_Tab_key_pressed.js on the new console frontend; r=Honza MozReview-Commit-ID: 1lq4QJ9JWb8
c85fbd16178d0844313ce0f5d8c43df9fc2fd73c: Bug 1406381 - Update the simple iteration progress calculation to match recent changes to the Web Animations specification; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 13 Oct 2017 12:31:21 +0900 - rev 386075
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1406381 - Update the simple iteration progress calculation to match recent changes to the Web Animations specification; r=hiro This implements the following change to the Web Animations specification: https://github.com/w3c/web-animations/pull/202/commits/19b6c33cee533dde34b67ac9e416d93ecf4cb1d0 The background to that change is described in the corresponding spec issue: https://github.com/w3c/web-animations/issues/201 MozReview-Commit-ID: GGA64LG5vT
bfd71e39abdebc3c78e95d36a83a9ae5ddfb84ac: Bug 1406381 - Add tests for simple iteration progress and current iteration when the playback rate is negative; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 13 Oct 2017 12:28:05 +0900 - rev 386074
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1406381 - Add tests for simple iteration progress and current iteration when the playback rate is negative; r=hiro MozReview-Commit-ID: H7cgEeGYUoj
7db086f55adba0e9ab9cd8e045da97bba3c808e1: Bug 1406381 - Extend assert_computed_timing_for_each_phase to accommodate negative playback rates; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 13 Oct 2017 12:27:56 +0900 - rev 386073
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1406381 - Extend assert_computed_timing_for_each_phase to accommodate negative playback rates; r=hiro MozReview-Commit-ID: LpTRS6aMaWw
2035e28610da7dddbf1d0cc377a6d6a4c551f1d2: Bug 1406381 - Factor out common code from simple-iteration-progress.html and current-iteration.html; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 13 Oct 2017 10:53:10 +0900 - rev 386072
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1406381 - Factor out common code from simple-iteration-progress.html and current-iteration.html; r=hiro This will become all the more necessary when we extend these definitions to work with negative playback rates. MozReview-Commit-ID: ITHEqjprWUy
05bea37339089f59a50640d966394b56705107fc: Bug 1406381 - Tidy up simple-iteration-progress.html and current-iteration.html somewhat; r=hiro
Brian Birtles <birtles@gmail.com> - Fri, 13 Oct 2017 10:45:58 +0900 - rev 386071
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1406381 - Tidy up simple-iteration-progress.html and current-iteration.html somewhat; r=hiro This is in preparation for further changes to these files later in this patch series. In particular this patch: * Moves some code to more modern Javascript that should be easier to read and maintain * Makes the tests more strict about when active/after values are specified - If the timing parameters mean there is no active phase, the test should not specify a value to test for that phase. If there *is* an active phase, the test must provide a value to test (if it does not the test will fails when it compares against the undefined value). - Likewise for the after phase This should make it a little easier to incorporate testing the playbackRate. MozReview-Commit-ID: 17vihK5RSbu
7ea4e2167179a2d54c479793091be3e5eca2b26f: servo: Merge #18859 - Update WR (mac gamma + alpha fix, 3d transform bug fixes) (from glennw:update-wr-3d-gamma); r=KiChjang
Glenn Watson <github@intuitionlibrary.com> - Thu, 12 Oct 2017 23:07:40 -0500 - rev 386070
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
servo: Merge #18859 - Update WR (mac gamma + alpha fix, 3d transform bug fixes) (from glennw:update-wr-3d-gamma); r=KiChjang Source-Repo: https://github.com/servo/servo Source-Revision: 1d0df04695f289015e6336e3caea8046a018fa06
fe68b3629d172031c55b9d969e33016f0b44a779: Bug 1282691 - Drop the assertion about an animation that we're making play-pending not already being pause-pending; r=boris
Brian Birtles <birtles@gmail.com> - Fri, 13 Oct 2017 14:37:51 +0900 - rev 386069
Push 32675 by archaeopteryx@coole-files.de at Fri, 13 Oct 2017 21:36:21 +0000
Bug 1282691 - Drop the assertion about an animation that we're making play-pending not already being pause-pending; r=boris We could handle this case by dropping the animation from the pause-pending table but that's an extra hashtable lookup that so far seems to be unnecessary. I have verified that the crashtest added in this patch fails without the code changes included here. MozReview-Commit-ID: Ed6u7WRLD2t
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip