Re: Testing Rust code in tree

Glean Team here. Can confirm that libxul-provided symbols aren't in rusttests builds at present (Rust stuff is built first then wrapped in the loving embrace of libxul). We do write rusttests in our crates that (currently) have no Gecko symbols (see toolkit/components/glean/api/), but have ended

Re: New and improved stack-fixing

This is wonderful news! The most recent time I interacted with this was tracking down a refcount leak. I was following the instructions at [1] which as of yet mention `fix_linux_stack.py`. Would you like me to file a bug for that to be fixed? I'd edit it directly, but I'm not confident I'd get

How To: Data Review in Components

Hello! We here in Data Stewardship have been receiving inquiries about how the Data Collection Review process[0] works now that more products are being built out of reusable components. What follows is a memo about how to approach Data Review when you're adding a data collection to a reusable

Shorter Data Collection Review Form For Renewals

Hello, In an effort to reduce the number of permanent data collections, the Data Stewardship Steering Committee has approved the addition of a new, short form (3 questions) for the purpose of making Data Collection renewals simpler.[1] Please feel welcome to use this form if you are renewing

"products" key now required for new Telemetry metrics

Hello, As part of the project to report GeckoView metrics in Fenix, we have made the `products` key required for metrics definitions in Histograms.json, Scalars.yaml, and Events.yaml. The products key identifies which "products" (for a hand-wavy definition of the word 'product') you want

Fwd: Changes to about:telemetry -- Now With Processes!

Hello! about:telemetry, the UI that allows you to browse current and historical Telemetry data in Firefox, is changing slightly. Starting with bug 1437446 (presently on autoland) it will default to showing you the Telemetry collected in all process types (previously it would show only the

Re: Input Delay Metric proposal

For in-the-wild input delay not specifically during pageload we also measure INPUT_EVENT_RESPONSE_DELAY_MS[1] and (from Firefox 53-60 and then resuscitated in 64) INPUT_EVENT_RESPONSE_COALESCED_MS[2] which record[3] from the time the OS created the input event until the time when the process is

Re: Event Telemetry now sent on "event" pings instead of "main" pings

More details in a more narrative-focused format can be found in the blog post here: https://chuttenblog.wordpress.com/2018/07/04/faster-event-telemetry-with-event-pings/ :chutten On Wed, Jun 27, 2018 at 10:02 AM Chris Hutten-Czapski wrote: > Hello, > > Due to a forecast increase

Event Telemetry now sent on "event" pings instead of "main" pings

Hello, Due to a forecast increase in demand for Event Telemetry, we have (via bug 1460595) moved Event Telemetry transmission from the "main" ping to special-purpose "event" pings. This has a couple of benefits, most notably that they are sent more often (less latency) and can also send more

Re: Update on rustc/clang goodness

Recently I found myself using the mozbuild-supplied clang for compiling Gecko on Linux (https://bugzilla.mozilla.org/show_bug.cgi?id=1451312). It works just peachily for me, and I find myself liking their error message decorators better than gcc's. Since we supply a compiler during bootstrap, it

Re: Use Counters were previously over-reporting, are now fixed.

e Fink <sf...@mozilla.com> wrote: > On 1/17/18 7:57 AM, Chris Hutten-Czapski wrote: > >> Hello, >> >>Use Counters[0] as reported by the Telemetry Aggregator (via the HTTPS >> API, and the aggregates dashboards on telemetry.mozilla.org) have been >> over-re

Use Counters were previously over-reporting, are now fixed.

Hello, Use Counters[0] as reported by the Telemetry Aggregator (via the HTTPS API, and the aggregates dashboards on telemetry.mozilla.org) have been over-reporting usage since bug 1204994[1] (about the middle of September, 2015). They are now fixed [2], and in the course of fixing it,

Re: Changes to tab min-width

I prefer the old behaviour, but I don't have a strong opinion on the matter. I think it's because I'm used to tab navigation by keyboard shortcut more than by mouse. I rearrange tabs so that they're close together. For everyone curious about how much of an outlier your subsessions are... on

Re: Retaining Nightly users after disabling of legacy extensions

For those interested, preliminary data shows a continuing increase in the Nightly population since 57. The number of users using Nightly 57 on August 17 was the highest number of users on any day on any Nightly version since... well, our data retention policy cuts out at 6 months, so since at

Re: GPU Process Experiment Results

My one-sentence summary of the article - If anything, the test cohort with the GPU process saw improved stability, especially for graphics crashes. Which is awesome! May need error bars for the figures to see how much of the results you saw we might have to attribute to the noise of reported

Re: Windows XP and Vista Long Term Support Plan

Over the past two months there has been no absolute decline in number of Windows XP installs. (Source: Tableau data, which is sadly not public so I cannot link because it reveals more data from our users than we feel comfortable sharing) Over the past two months there has been an absolute

Re: Help ridding tests of unsafe CPOWs

Things that would help me help with this endeavour: 1: A bug to file patches against 2: A method for detecting if our fix actually fixes the problem I presume a skeleton of what we're looking for is: 1) Use DXR/ls -r/whatever to find the test file in the tree 2) On the line number(s) mentioned,

Re: W3C Proposed Recommendation: HTML 5.1

Can you provide any details (either inline, or a sampling of links) to summarize the broader concerns that might not be encapsulated in the document itself? On Mon, Oct 10, 2016 at 9:46 PM, L. David Baron wrote: > A W3C Proposed Recommendation is available for the membership