Re: Intent to Implement and Ship: Make MOZ_QUIET the default, require opt-in for DOMWINDOW/DOCSHELL logs

2019-11-08 Thread Dave Townsend
Thank you for doing this.

On Fri, Nov 8, 2019 at 2:44 PM Tom Ritter  wrote:

> In https://bugzilla.mozilla.org/show_bug.cgi?id=1592297 I plan/hope to
> remove MOZ_QUIET and turn off the DOCSHELL/DOMWINDOW logging by default.
> It will automatically be enabled in browser-chrome tests where it is
> needed. (It actually will no longer be possible to disable it when running
> those tests also.)
>
> Once this lands, MOZ_QUIET will no longer do anything, and if you want this
> output you will need to explicitly set a new env var.  (Current idea is
> MOZ_LOG_WINDOWS_DOCSHELLS but feel free to tell me what color for the
> bikeshed in phabricator, I have no preference.)
>
> I'm sending this before I finish the requested changes in phabricator to
> give folks an opportunity to raise objections; I hope to land it mid/late
> next week.
>
> -tom
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Intent to Implement and Ship: Make MOZ_QUIET the default, require opt-in for DOMWINDOW/DOCSHELL logs

2019-11-08 Thread Tom Ritter
In https://bugzilla.mozilla.org/show_bug.cgi?id=1592297 I plan/hope to
remove MOZ_QUIET and turn off the DOCSHELL/DOMWINDOW logging by default.
It will automatically be enabled in browser-chrome tests where it is
needed. (It actually will no longer be possible to disable it when running
those tests also.)

Once this lands, MOZ_QUIET will no longer do anything, and if you want this
output you will need to explicitly set a new env var.  (Current idea is
MOZ_LOG_WINDOWS_DOCSHELLS but feel free to tell me what color for the
bikeshed in phabricator, I have no preference.)

I'm sending this before I finish the requested changes in phabricator to
give folks an opportunity to raise objections; I hope to land it mid/late
next week.

-tom
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Phabricator Update Moved to Tuesday 10:00 AM EST

2019-11-08 Thread David Lawrence
Normally we do Phabricator release updates for 
phabricator.services.mozilla.com on Mondays at 10:00 AM EST. This coming

weeks update will occur Tuesday at the same time instead.

Thanks
dkl

--
David Lawrence
d...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Reminder: Planned Taskcluster migration this weekend (Nov 9)

2019-11-08 Thread James Graham

On 04/11/2019 22:00, Chris Cooper wrote:

tl;dr:

Taskcluster, the platform supporting Firefox CI, will be moving to a new 
hosting environment during the tree closing window (TCW) this coming Saturday, 
Nov 9. Trees will be closed from 14:00 UTC to 23:00 UTC. CI services will be 
available as soon as possible thereafter, pending verification of the new setup.


I'd just like to call out how great the TaskCluster team have been at 
helping projects moving to the community instance.


We have just finished moving the upstream wpt testing to the new setup, 
and the TaskCluster team proactively made sure we were aware the change 
was happening, tried to identify likely issues in our setup, filed PRs 
for the most obvious changes, and made sure we were on track to finish 
by the deadline. They also helped us work through teething issues once 
we were running on the new instance.


Overall the experience has been as good as you could wish for with a 
large infrastructure change. Thanks to everyone involved; I hope the 
Gecko migration goes just as smoothly!

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: PSA: changes to numerous DOM components on Bugzilla

2019-11-08 Thread Emilio Cobos Álvarez

On 11/8/19 10:26 AM, Anne van Kesteren wrote:

Heya,

In https://bugzilla.mozilla.org/show_bug.cgi?id=1594717 the DOM team
requested quite a number of changes to their various components in
Mozilla's Bugzilla. Those components are now prefixed with either
"DOM:" or "Storage:". Please keep this in mind if you can't find a
component in its usual place.


Thanks for the PSA.

I sent https://github.com/mozilla-frontend-infra/codetribute/pull/358 to 
update the codetribute site so that good-first-bugs from those 
components appear there.


 -- Emilio


Thanks to everyone who helped with this cleanup and please let me know
if you have any questions or further suggestions.

Kind regards,

Anne
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


PSA: changes to numerous DOM components on Bugzilla

2019-11-08 Thread Anne van Kesteren
Heya,

In https://bugzilla.mozilla.org/show_bug.cgi?id=1594717 the DOM team
requested quite a number of changes to their various components in
Mozilla's Bugzilla. Those components are now prefixed with either
"DOM:" or "Storage:". Please keep this in mind if you can't find a
component in its usual place.

Thanks to everyone who helped with this cleanup and please let me know
if you have any questions or further suggestions.

Kind regards,

Anne
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform