da3671e1528ca68d94ffde570f5c35129ca9eeaf: Bug 1323115 - Enable BaselineJIT on aarch64. r=jandem,jolesen
Denis Scott <denis.scott.v@gmail.com> - Fri, 23 Dec 2016 15:45:12 +0100 - rev 453470
Push 39687 by bmo:ntim.bugs@gmail.com at Fri, 23 Dec 2016 16:10:52 +0000
Bug 1323115 - Enable BaselineJIT on aarch64. r=jandem,jolesen
981fd29c57012c7e8a28168ca0941e00be560462: Bug 1322093 followup - Make idempotent ICs handle unshadowed DOM proxies to fix Dromaeo regressions. r=evilpie on IRC
Jan de Mooij <jdemooij@mozilla.com> - Fri, 23 Dec 2016 15:17:32 +0100 - rev 453469
Push 39687 by bmo:ntim.bugs@gmail.com at Fri, 23 Dec 2016 16:10:52 +0000
Bug 1322093 followup - Make idempotent ICs handle unshadowed DOM proxies to fix Dromaeo regressions. r=evilpie on IRC
94dfb2c98d9ca64d986c0baff2abdd782c6bead7: Bug 1321020 Part 2: Test that a file:// URI window opened from a file:// page can be navigated to web content. r=gijs
Bob Owen <bobowencode@gmail.com> - Fri, 23 Dec 2016 12:27:03 +0000 - rev 453468
Push 39687 by bmo:ntim.bugs@gmail.com at Fri, 23 Dec 2016 16:10:52 +0000
Bug 1321020 Part 2: Test that a file:// URI window opened from a file:// page can be navigated to web content. r=gijs
b50562f277da2f968c24b25e81253ad12c0fb7ee: Bug 1321020 Part 1: Ensure that a new tab opened from content with non-default remote type, gets correct remote type. r=gijs
Bob Owen <bobowencode@gmail.com> - Fri, 23 Dec 2016 12:27:03 +0000 - rev 453467
Push 39687 by bmo:ntim.bugs@gmail.com at Fri, 23 Dec 2016 16:10:52 +0000
Bug 1321020 Part 1: Ensure that a new tab opened from content with non-default remote type, gets correct remote type. r=gijs
2a762f5632902fe62907175d2872c2c307cf9ef8: Bug 1302441 - Break assertion down into smaller assertions. r=shu
Jim Blandy <jimb@mozilla.com> - Tue, 20 Dec 2016 23:37:52 -0800 - rev 453466
Push 39687 by bmo:ntim.bugs@gmail.com at Fri, 23 Dec 2016 16:10:52 +0000
Bug 1302441 - Break assertion down into smaller assertions. r=shu
dcf605112d818f2a09de56fc03676235b588b081: Bug 1325623 - Fix most no-undef eslint issues in toolkit/components. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Fri, 23 Dec 2016 16:00:46 +0000 - rev 453465
Push 39686 by bmo:standard8@mozilla.com at Fri, 23 Dec 2016 16:04:09 +0000
Bug 1325623 - Fix most no-undef eslint issues in toolkit/components. r?Mossop MozReview-Commit-ID: DYJa1uNVagw
4ab46c0c09e2ce2ae9050dce67a9862b7c54bd6e: Bug 1325623 - Fix most no-undef eslint issues in toolkit/components. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Fri, 23 Dec 2016 16:00:46 +0000 - rev 453464
Push 39685 by bmo:standard8@mozilla.com at Fri, 23 Dec 2016 16:03:45 +0000
Bug 1325623 - Fix most no-undef eslint issues in toolkit/components. r?Mossop MozReview-Commit-ID: DYJa1uNVagw
7631d9fdec2f30b6aab32039108899c1e6d451b7: Bug 1325623 - Fix most no-undef eslint issues in toolkit/components. r?Mossop draft
Mark Banner <standard8@mozilla.com> - Fri, 23 Dec 2016 16:00:46 +0000 - rev 453463
Push 39684 by bmo:standard8@mozilla.com at Fri, 23 Dec 2016 16:01:40 +0000
Bug 1325623 - Fix most no-undef eslint issues in toolkit/components. r?Mossop MozReview-Commit-ID: DYJa1uNVagw
c57ce476875b19b99ef9e2dcf66df1274809fa54: Bug 1322873 - Bug 1322873 - Add React event bubbles to the Markup View r=tromey draft
Michael Ratcliffe <mratcliffe@mozilla.com> - Mon, 19 Dec 2016 11:23:49 +0000 - rev 453462
Push 39683 by bmo:mratcliffe@mozilla.com at Fri, 23 Dec 2016 15:41:44 +0000
Bug 1322873 - Bug 1322873 - Add React event bubbles to the Markup View r=tromey DevRel have made it clear that one of the number one complaints they hear is that we are not supporting React in our tools. So how about we have our event bubbles include React events and allow people to go to the event listener source in the debugger? I don't believe that any other tool does this so it is totally worth doing... and in time for Christmas as well ;) Works just fine in development and production versions of React. It also works in the browser toolbox so it can be used to debug events in our own tools e.g. The Debugger. The files under devtools/client/inspector/markup/test/ are either test or React library files so they only really need a cursory glance. This means that you should focus on the following files when reviewing: - devtools/client/locales/en-US/inspector.properties - devtools/client/shared/widgets/tooltip/EventTooltipHelper.js - devtools/server/actors/inspector.js - devtools/server/event-parsers.js Now allowed the use of JSX in mochitests and fixed all eslint errors. MozReview-Commit-ID: AtxhainieQe
bb8e10db9c72ce4a99cfa90611bbfc0d66ccc1be: Bug 1325148 - Temporarily disable leakchecking in crashtests on linux, r?jmaher draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 21 Dec 2016 17:06:29 -0500 - rev 453461
Push 39682 by ahalberstadt@mozilla.com at Fri, 23 Dec 2016 15:28:48 +0000
Bug 1325148 - Temporarily disable leakchecking in crashtests on linux, r?jmaher This is being disabled because of the leak in bug 1325215. It slipped in because leak checking in reftest was temporarily failing to turn the job orange. We are disabling leak checking so we can land the fix ASAP and prevent further bustage from slipping through in the mean time. Once bug 1325215 has been fixed, this should be backed out. MozReview-Commit-ID: 74VGhHvZtIG
fec947b535ae6a4458d6da32f64b9cf88aea9a4b: Bug 1325148 - Temporarily disable mochitest leakchecking for directories containing known leaks, r?jmaher draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 21 Dec 2016 16:22:50 -0500 - rev 453460
Push 39682 by ahalberstadt@mozilla.com at Fri, 23 Dec 2016 15:28:48 +0000
Bug 1325148 - Temporarily disable mochitest leakchecking for directories containing known leaks, r?jmaher Leak checking in mochitest was failing to turn the jobs orange for a period of time. Several leaks slipped through in the interim. In order to land the fix ASAP to avoid further bustage, these leaks are being whitelisted. See the patch or the dependency graph of bug 1325148 for the list of leaks/bugs that are being disabled. While these bugs won't show up in treeherder, they are a priority to fix, as they could represent leaks that are already landed in the code. MozReview-Commit-ID: JY7Gpvswp4r
1f85e728e1617264d65e34c2abdad453f6e76aa3: Bug 1325148 - Temporarily disable leakchecking in crashtests on linux, r?jmaher draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 21 Dec 2016 17:06:29 -0500 - rev 453459
Push 39681 by ahalberstadt@mozilla.com at Fri, 23 Dec 2016 15:24:29 +0000
Bug 1325148 - Temporarily disable leakchecking in crashtests on linux, r?jmaher This is being disabled because of the leak in bug 1325215. It slipped in because leak checking in reftest was temporarily failing to turn the job orange. We are disabling leak checking so we can land the fix ASAP and prevent further bustage from slipping through in the mean time. Once bug 1325215 has been fixed, this should be backed out. MozReview-Commit-ID: 74VGhHvZtIG
8d1de70eddecb95c1bf096ead9507b48c01cdea6: Bug 1325148 - Temporarily disable mochitest leakchecking for directories containing known leaks, r?jmaher draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 21 Dec 2016 16:22:50 -0500 - rev 453458
Push 39681 by ahalberstadt@mozilla.com at Fri, 23 Dec 2016 15:24:29 +0000
Bug 1325148 - Temporarily disable mochitest leakchecking for directories containing known leaks, r?jmaher Leak checking in mochitest was failing to turn the jobs orange for a period of time. Several leaks slipped through in the interim. In order to land the fix ASAP to avoid further bustage, these leaks are being whitelisted. See the patch or the dependency graph of bug 1325148 for the list of leaks/bugs that are being disabled. While these bugs won't show up in treeherder, they are a priority to fix, as they could represent leaks that are already landed in the code. MozReview-Commit-ID: JY7Gpvswp4r
383671a7a73a7ffb83da6b4376f743c5cd1f23aa: Bug 1325148 - Use "error" level in mozleak when logging leak failures, r?jgraham draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 21 Dec 2016 14:02:04 -0500 - rev 453457
Push 39681 by ahalberstadt@mozilla.com at Fri, 23 Dec 2016 15:24:29 +0000
Bug 1325148 - Use "error" level in mozleak when logging leak failures, r?jgraham This fixes a regression when switching to the StructuredOutputParser in mozharness. Previously, mozleak was relying on the string "TEST-UNEXPECTED-FAIL" to turn the jobs orange, but it was doing so at the "warning" level. The StructuredOutputParser requires the "error" level to set the appropriate tbpl_status. MozReview-Commit-ID: 9u9mwqrkA6E
5a0fc4da17b67c3e7fec885434b135162edd3c0b: Bug 1325148 - Temporarily disable leakchecking in crashtests on linux, r?jmaher draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 21 Dec 2016 17:06:29 -0500 - rev 453456
Push 39680 by ahalberstadt@mozilla.com at Fri, 23 Dec 2016 15:22:14 +0000
Bug 1325148 - Temporarily disable leakchecking in crashtests on linux, r?jmaher This is being disabled because of the leak in bug 1325215. It slipped in because leak checking in reftest was temporarily failing to turn the job orange. We are disabling leak checking so we can land the fix ASAP and prevent further bustage from slipping through in the mean time. Once bug 1325215 has been fixed, this should be backed out. MozReview-Commit-ID: 74VGhHvZtIG
2712923f40b41c41b1009f0c00d26b80e9dc9f69: Bug 1325148 - Temporarily disable mochitest leakchecking for directories containing known leaks, r?jmaher draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 21 Dec 2016 16:22:50 -0500 - rev 453455
Push 39680 by ahalberstadt@mozilla.com at Fri, 23 Dec 2016 15:22:14 +0000
Bug 1325148 - Temporarily disable mochitest leakchecking for directories containing known leaks, r?jmaher Leak checking in mochitest was failing to turn the jobs orange for a period of time. Several leaks slipped through in the interim. In order to land the fix ASAP to avoid further bustage, these leaks are being whitelisted. See the patch or the dependency graph of bug 1325148 for the list of leaks/bugs that are being disabled. While these bugs won't show up in treeherder, they are a priority to fix, as they could represent leaks that are already landed in the code. MozReview-Commit-ID: JY7Gpvswp4r
b38673ce1f3274f67b85bee7919cfb67e0abc53e: Bug 1325148 - Use "error" level in mozleak when logging leak failures, r?jgraham draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 21 Dec 2016 14:02:04 -0500 - rev 453454
Push 39680 by ahalberstadt@mozilla.com at Fri, 23 Dec 2016 15:22:14 +0000
Bug 1325148 - Use "error" level in mozleak when logging leak failures, r?jgraham This fixes a regression when switching to the StructuredOutputParser in mozharness. Previously, mozleak was relying on the string "TEST-UNEXPECTED-FAIL" to turn the jobs orange, but it was doing so at the "warning" level. The StructuredOutputParser requires the "error" level to set the appropriate tbpl_status. MozReview-Commit-ID: 9u9mwqrkA6E
8e499599cf9756962bdc54a610e5c68226e4a05f: Bug 1274891 - Part 5: Introduce nsRestyleHint::None. draft
Boris Chiou <boris.chiou@gmail.com> - Fri, 23 Dec 2016 15:19:57 +0800 - rev 453453
Push 39679 by bmo:boris.chiou@gmail.com at Fri, 23 Dec 2016 15:19:32 +0000
Bug 1274891 - Part 5: Introduce nsRestyleHint::None. We use enum class now, so I think it's better to replace nsRestyleHint(0) with nsRestyleHint::None. Let both nsChangeHint and nsRestyleHint use |None| as 0. MozReview-Commit-ID: KSbm6OZPumr
96d0ee408d76cd73d6b5dcacdaf07c0f898e3f17: Bug 1274891 - Part 4: Use enum class for nsRestyleHint. draft
Boris Chiou <boris.chiou@gmail.com> - Thu, 22 Dec 2016 18:53:35 +0800 - rev 453452
Push 39679 by bmo:boris.chiou@gmail.com at Fri, 23 Dec 2016 15:19:32 +0000
Bug 1274891 - Part 4: Use enum class for nsRestyleHint. MozReview-Commit-ID: DtzICOLIFDD
706a01301f5d5911403a75832c4d4c40078d5d83: Bug 1274891 - Part 3: Move macros into nsChangeHint enum class. draft
Boris Chiou <boris.chiou@gmail.com> - Thu, 22 Dec 2016 10:49:07 +0800 - rev 453451
Push 39679 by bmo:boris.chiou@gmail.com at Fri, 23 Dec 2016 15:19:32 +0000
Bug 1274891 - Part 3: Move macros into nsChangeHint enum class. And use all caps to nsChangeHint_Hints_NotHandledForDescendants to follow the coding style for macros. MozReview-Commit-ID: BHRDYNMdMnc
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip