This is only used from the "late writes" section, which is only rendered if there are late writes. https://searchfox.org/mozilla-central/rev/15b656909e77d3048d4652b894f79a8c719b4b86/toolkit/content/aboutTelemetry.js#2341-2344 The relevant lines have no coverage in automated tests... This seems unfortunate - from a very quick look, this is currently tricky to do - perhaps the simplest thing would be to have a way to clear the telemetry cache, then write dummy late write stack data into the profile directory, then async fetch the telemetry data and then open `about:telemetry`. As it is, AFAICT if there _are_ late writes, `about:telemetry` will partially break, losing origin telemetry and simple measurements. Given Avery worked on this as an MSU student 3 years ago, I think we're unlikely to hear back from him - passing needinfo to chutten as this breakage is probably relevant to his interests...
Bug 1780167 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is only used from the "late writes" section, which is only rendered if there are late writes. https://searchfox.org/mozilla-central/rev/15b656909e77d3048d4652b894f79a8c719b4b86/toolkit/content/aboutTelemetry.js#2341-2344 The relevant lines have no coverage in automated tests because there are no late writes... This seems unfortunate - from a very quick look, this is currently tricky to do - perhaps the simplest thing would be to have a way to clear the telemetry cache, then write dummy late write stack data into the profile directory, then async fetch the telemetry data and then open `about:telemetry`. As it is, AFAICT if there _are_ late writes, `about:telemetry` will partially break, losing origin telemetry and simple measurements. Given Avery worked on this as an MSU student 3 years ago, I think we're unlikely to hear back from him - passing needinfo to chutten as this breakage is probably relevant to his interests...