Re: Crash signature change: signatures now include abort messages

Thanks Benjamin! Here's a search that shows what those new signatures look like on stage: https://crash-stats.allizom.org/search/?product=Firefox=%5EAbort&_facets=abort_message&_columns=date&_columns=signature&_columns=abort_message Please let me know if that seems good or not before we push

Re: Triage Plan for Firefox Components

Sorry to be dense, but if I understand correctly, you'd like to: 1. Have a policy that all of Gecko needs to triage bugs in a certain way. 2. Redefine how everyone defines priorities? And you think that 24 hours is enough time to get consensus on that. Do I have that right? -Ekr On Wed, Apr

Re: Triage Plan for Firefox Components

On Fri, Apr 1, 2016 at 9:45 AM, James Graham wrote: > But once we have picked something, can we at least try to remove any UI > that is more-or-less vestigial given that decision and, at least briefly, > fight entropy by making things simpler and more consistent, rather

Re: Crash signature change: signatures now include abort messages

On Wed, Apr 6, 2016 at 2:34 PM, Benjamin Smedberg wrote: > No, it does not catch MOZ_RELEASE_ASSERT, because that doesn't call > NS_DebugBreak and that is what does the AbortMessage annotation[1]. > NS_RUNTIMEABORT is the recommended way to reliably crash if you're in >

Re: Crash signature change: signatures now include abort messages

No, it does not catch MOZ_RELEASE_ASSERT, because that doesn't call NS_DebugBreak and that is what does the AbortMessage annotation[1]. NS_RUNTIMEABORT is the recommended way to reliably crash if you're in XPCOM-y code. Bug 1104682 is filed for this, though. I'd love for somebody to take this.

Re: Crash signature change: signatures now include abort messages

Does this catch MOZ_RELEASE_ASSERT and similar? It would be nice to distinguish those somehow in crash-stats. - Kyle On Wed, Apr 6, 2016 at 2:18 PM, Benjamin Smedberg wrote: > A change just landed which will change the way crash signatures are > computed for intentional

Crash signature change: signatures now include abort messages

A change just landed which will change the way crash signatures are computed for intentional aborts. Previously the crash signature would be "NS_DebugAbort | ". Now the signature will be "Abort | | ". This should make it much easier to distinguish various classes of abort. Thanks to Adrian

Re: Upcoming SSH Host Key Rotation for hg.mozilla.org

On 05/04/2016 09:09, Philip Chee wrote: > On 04/04/2016 23:52, Gregory Szorc wrote: >> We also changed the SSH server config to only support the "modern" set of >> ciphers, MACs, algorithms, etc from >> https://wiki.mozilla.org/Security/Guidelines/OpenSSH#Modern. If you are >> running an old SSH

Re: Triage Plan for Firefox Components

On Tue, Apr 5, 2016 at 9:27 PM, Emma Humphries wrote: > It's been a week since I asked for your comments on the plan for triage, > thank you. > > I'm going reply to some general comments on the plan, and outline next > steps. > > Ekt and others said that up to now, individual

Re: Upcoming SSH Host Key Rotation for hg.mozilla.org

On 05/04/2016 14:23, Onno Ekker wrote: > Op 5-4-2016 om 3:09 schreef Philip Chee: >> I'm using TortoiseHg whichh uses PuTTY and PLINK internally. I've >> deleted the mozilla host key and accepted the new one. >> >> Now I can't push to comm-central via TortoiseHg. I can't push directly >> via

Re: CSS Triggers

On Wed, Feb 24, 2016 at 8:53 AM, Boris Zbarsky wrote: > On 2/23/16 4:18 PM, Jordan Santell wrote: > >> are there any other suggestions on how we >> can observe this data and minimize incorrect results? >> > > In an automated way, or manually? > > Because you can look at

Re: CSS Triggers

Hi! Should these 3 bits of information (trigger reflow, paint or compositing) also be displayed on each MDN page related to a CSS property? -- Jean-Yves Perrier Senior St. Project Manager, Developer Documentation / MDN On 23/02/2016 21:18, Jordan Santell wrote: Awhile back, Google's Paul