4fe99b113fff368afa155646b5def098e9706880: Bug 1369840 - Support getting the compositor-side APZ test data over PWebRenderBridge. r=botond
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 02 Jun 2017 16:19:33 -0400 - rev 412606
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369840 - Support getting the compositor-side APZ test data over PWebRenderBridge. r=botond This is fairly straightforward plumbing. The webrender equivalent of PLayerTransaction is PWebRenderBridge and we can use that to get the compositor-side APZTestData. MozReview-Commit-ID: JE9WkmejuM9
3fccc08e0486e07c104757a3233eb24a5e5677d2: Bug 1369840 - Modify CompositorBridgeParentBase::GetAPZTestData to take a layers id instead of a transaction parent. r=botond
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 02 Jun 2017 16:19:33 -0400 - rev 412605
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369840 - Modify CompositorBridgeParentBase::GetAPZTestData to take a layers id instead of a transaction parent. r=botond This allows us to use it from WebRenderBridgeParent which doesn't have a LayerTransactionParent instance. MozReview-Commit-ID: KokYS6gcXhs
e70cb7378a1f0f4b239fb34573655289e0ce71b0: No bug - Revendor rust dependencies
Servo VCS Sync <servo-vcs-sync@mozilla.com> - Sat, 03 Jun 2017 01:39:44 +0000 - rev 412604
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
No bug - Revendor rust dependencies
60dd8367c496d7b177d0672ed455ac1848db9e00: servo: Merge #17145 - Bump cssparser (from Manishearth:bump); r=mbrubeck
Manish Goregaokar <manishsmail@gmail.com> - Fri, 02 Jun 2017 17:46:35 -0700 - rev 412603
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
servo: Merge #17145 - Bump cssparser (from Manishearth:bump); r=mbrubeck Source-Repo: https://github.com/servo/servo Source-Revision: 985050d3645382d5c2cc6bd6819ab05f9b843331
34970c739b2eaac9158dd67fe2980d2fbd850637: Merge m-c to autoland, a=merge
Wes Kocher <wkocher@mozilla.com> - Fri, 02 Jun 2017 17:29:12 -0700 - rev 412602
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Merge m-c to autoland, a=merge MozReview-Commit-ID: 3oLjBFfMQdZ
60b41398d6c261f0906baa51014f6461a21d298b: Bug 1369828 - Fuzz native-theme/492155-4.html during stylo-vs-gecko comparison. r=mstange
Botond Ballo <botond@mozilla.com> - Fri, 02 Jun 2017 16:19:33 -0400 - rev 412601
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369828 - Fuzz native-theme/492155-4.html during stylo-vs-gecko comparison. r=mstange MozReview-Commit-ID: EgqzsLid5im
72ab73cbc5c7d6f18d55a855103e48d7a8bb7eae: Bug 1369892 - Silence findbugs dodgy casting warning r=nalexander
Grigory Kruglov <gkruglov@mozilla.com> - Fri, 02 Jun 2017 18:15:32 -0400 - rev 412600
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369892 - Silence findbugs dodgy casting warning r=nalexander Strangely enough, this patch seems to appease findbugs. While dodgy indeed, I think this casting is acceptable in this case since we control both sides of the equation (sender & receiver of telemetry), but can't easily do away with casting. MozReview-Commit-ID: FBTkRqKPtxt
4f5b93b0571a23c8314233534b06a1aeb476fb1e: Bug 1369891 - Improve sync ping tests and stop them from failing in automation r=nalexander
Grigory Kruglov <gkruglov@mozilla.com> - Fri, 02 Jun 2017 19:10:59 -0400 - rev 412599
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369891 - Improve sync ping tests and stop them from failing in automation r=nalexander Switch to explicit checks of contents of json objects, vs checking against toString output. MozReview-Commit-ID: A9YqG3A2My5
eb1d5848152b5f0cb2eeff48bce5996410a3597b: servo: Merge #15354 - Redirect document loads manually (from cynicaldevil:manual-redirect); r=jdm
Nikhil Shagrithaya <nikhilshagri@gmail.com> - Fri, 02 Jun 2017 14:49:21 -0700 - rev 412598
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
servo: Merge #15354 - Redirect document loads manually (from cynicaldevil:manual-redirect); r=jdm <!-- Please describe your changes on the following line: --> --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] These changes fix #14596 . r? @jdm I ran some tests at random from the `navigating-across-documents` folder, and they are passing. <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> Source-Repo: https://github.com/servo/servo Source-Revision: eac4f407e2bfa0055a698ca438972566f0814e43
ea498127969f442dba5cd81ac554bca5f9490d99: Bug 1369806: Fix up pkix test to correctly pass zero to CreateEncodedBasicConstraints (which takes a pointer-to-long, rather than a long). r=keeler
Daniel Holbert <dholbert@cs.stanford.edu> - Fri, 02 Jun 2017 13:21:53 -0700 - rev 412597
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369806: Fix up pkix test to correctly pass zero to CreateEncodedBasicConstraints (which takes a pointer-to-long, rather than a long). r=keeler MozReview-Commit-ID: Ki8AHuW5zyP
95432b49cac4e582c9d84907ea1c3bfd1fd2ff52: Bug 1369864: Suppress clang -Wno-zero-as-null-pointer-constant build warning, in pkix/test/gtest. r=keeler
Daniel Holbert <dholbert@cs.stanford.edu> - Fri, 02 Jun 2017 13:05:30 -0700 - rev 412596
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369864: Suppress clang -Wno-zero-as-null-pointer-constant build warning, in pkix/test/gtest. r=keeler The gtest headers trigger many instances of this warning, due to their usage of NULL instead of nullptr. MozReview-Commit-ID: Dhv7mPHpZ7I
85f41e26f8b6e85b0d5ded8c182c5a6667968985: Bug 1369837: Add a void cast to silence clang Wcomma build warning, in sandbox's snapshot of chromium header. r=bobowen
Daniel Holbert <dholbert@cs.stanford.edu> - Fri, 02 Jun 2017 12:45:01 -0700 - rev 412595
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369837: Add a void cast to silence clang Wcomma build warning, in sandbox's snapshot of chromium header. r=bobowen The build warning is for "possible misuse of comma operator". The comma operator is a bit of a footgun becasue its first operand's result just gets dropped on the floor (in this case, the result of the DCHECK expression). It appears that Chromium's use of the comma operator here is intentional, though -- so we might as well accept clang's suggestion and "cast expression to void to silence warning". This is also filed upstream as: https://bugs.chromium.org/p/chromium/issues/detail?id=729123 MozReview-Commit-ID: Al2xsYEo3p0
d9b7971a270cde0cff0adbe068707fd6f92f5028: Bug 1321847 - Add new linux jobs using the baseline of supported toolchains. r=mshal
Mike Hommey <mh+mozilla@glandium.org> - Fri, 02 Jun 2017 11:34:46 +0900 - rev 412594
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1321847 - Add new linux jobs using the baseline of supported toolchains. r=mshal For a long time, we've kind of forced the GCC version used to compile Firefox on automation to the minimum version we do support, because using a newer version would pretty much guarantee that builds with older versions would break. Ideally, the same would be true of rust, but it's not the case, and sure enough, building with older versions breaks. The most recent example is bug 1367734 making rustc 1.17.0 required but leaving configure checking for version 1.15.1. There are multiple reasons why we'd want to use newer versions of rust to build shipping versions of Firefox other than language requirements, but we should still ensure building with supported versions of rust doesn't break silently. Here we add a set of new linux jobs that build opt and debug build with the baseline of supported toolchains. At the moment, that's GCC 4.9, rust 1.15.1, and clang 3.9 (for bindgen). That's a copy of the current toolchains used for normal linux jobs, with rustc downgraded to the package used after bug 1338311. Further down the line, we'll be able to bump the versions of GCC, rust and/or clang for the shipped Firefox builds, while keeping those jobs on GCC 4.9, rust 1.15.1 and clang 3.9, until we do intentionally want to bump those versions (as well as the corresponding configure checks).
4db381159f27a7d1a1b5d112be7441290dc12550: Bug 1321847 - Allow to override the mozharness tooltool manifest from the environment. r=mshal
Mike Hommey <mh+mozilla@glandium.org> - Fri, 02 Jun 2017 11:28:26 +0900 - rev 412593
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1321847 - Allow to override the mozharness tooltool manifest from the environment. r=mshal The main motivation behind this change is that going towards toolchain tasks hooked up in the task graph (bug 1313111), we're going to end up with jobs using both taskcluster toolchain job and tooltool artifacts for their toolchain needs. With the current setup, this means the toolchain dependencies will be spread between taskcluster task graph definition and mozharness configuration. It also makes things more complex to provide a command that pulls the right toolchains from both taskcluster and tooltool (bug 1356529), because one needs to find and parse the mozharness config (which also happens to be python code that uses platform-specific things, so e.g. reading windows mozharness config fails on other platforms). All in all, moving the tooltool manifest path to the taskcluster task definitions would make things simpler, and would also allow make patches switching from tooltool to taskcluster artifacts more straightforward to validate. But since some build types still run on buildbot, we'll have to keep part of the current setup using mozharness configs. So we allow to override the tooltool manifest path from the environment, and we'll rely on taskcluster task definitions being able to set environment variables. Actually moving the relevant tooltool manifest paths from mozharness config to taskcluster task definitions is left for a followup. Another followup is to move the tooltool manifest paths declared in some ad-hoc build scripts to taskcluster task definitions as well. The immediate need for this, though, is to allow to have duplicated jobs that only differ in their tooltool manifest, without duplicating a complete mozharness config that will end up stale (the goal being that really only the tooltool manifest differs, even when the original jobs change).
2c0e0f3062aeb2e1bca2b743ab0d82ca19619c9e: Bug 1365554 - Fix storage inspector failures in browser_devtools_api.js r=jdescottes
Michael Ratcliffe <mratcliffe@mozilla.com> - Fri, 02 Jun 2017 14:15:41 +0100 - rev 412592
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1365554 - Fix storage inspector failures in browser_devtools_api.js r=jdescottes The changes to devtools/client/framework/test/browser_devtools_api.js are purely eslint fixes so you only need to glance over them. The changes to ui.js checks if the toolbox is being destroyed... if it is we don't log an error, otherwise we do. MozReview-Commit-ID: JJTqkYXVsYG
3c59f4cceb9a7f4acca9331409c91d148405382c: Bug 1338860 fix onErrorOccurred to handle some additional errors, r=aswan,kmag
Shane Caraveo <scaraveo@mozilla.com> - Fri, 02 Jun 2017 14:16:48 -0700 - rev 412591
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1338860 fix onErrorOccurred to handle some additional errors, r=aswan,kmag MozReview-Commit-ID: I5uZmhWFBUd
5092c00facfaacf3f761a5c9384b1b639d5de41d: Bug 1367923 - Enable link attr tests for Stylo. r=Manishearth
J. Ryan Stinnett <jryans@gmail.com> - Thu, 01 Jun 2017 17:42:19 -0500 - rev 412590
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1367923 - Enable link attr tests for Stylo. r=Manishearth MozReview-Commit-ID: 9wkSpx7h0km
7b8fcdae113f0fa1c1c0ccc6dcdc0d2602501c7e: Bug 1367923 - Store Servo decls when link preshints change. r=Manishearth
J. Ryan Stinnett <jryans@gmail.com> - Thu, 01 Jun 2017 13:37:02 -0500 - rev 412589
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1367923 - Store Servo decls when link preshints change. r=Manishearth When any of the link preshints (link, vlink, alink) on <body> are set, we store a Servo declaration block to hold the color from the hint. This uses a one-off approach instead of `nsMappedAttributes` that is used for other preshints because it depends on element state and also it affects links through the document (as opposed to the element where the attribute is set). MozReview-Commit-ID: KUvyCq9KfHT
ac5fcb551e41400cdaad4a9659e33c1852edcd31: servo: Merge #17144 - Stylo: Support link preshints on <body> (from jryans:link-pres-hints); r=Manishearth
J. Ryan Stinnett <jryans@gmail.com> - Fri, 02 Jun 2017 13:08:04 -0700 - rev 412588
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
servo: Merge #17144 - Stylo: Support link preshints on <body> (from jryans:link-pres-hints); r=Manishearth https://bugzilla.mozilla.org/show_bug.cgi?id=1367923 Source-Repo: https://github.com/servo/servo Source-Revision: 54448305de3048f23004de0d9ee84efd25af8a79
3226b56675ffdb2af7790e13a5a4b927ceb0b063: Bug 1369871: Add "const" keyword to a long* param in a pkix test function. r=keeler
Daniel Holbert <dholbert@cs.stanford.edu> - Fri, 02 Jun 2017 13:45:41 -0700 - rev 412587
Push 1490 by mtabara@mozilla.com at Mon, 31 Jul 2017 14:08:16 +0000
Bug 1369871: Add "const" keyword to a long* param in a pkix test function. r=keeler The only reason this param is a pointer is so that it can be optional. It's not an outparam -- the function does not (and does not intend to) modify it -- so it should be declared as 'const' to make that clearer & to allow clients to pass in pointers to const values. MozReview-Commit-ID: HbF96YNfnSt
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip