Closed Bug 1595546 Opened 5 years ago Closed 5 years ago

baseline.duration errors still exist on glean-core

Categories

(Data Platform and Tools :: Glean: SDK, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mdroettboom, Unassigned)

References

Details

(Whiteboard: [telemetry:glean-rs:backlog])

At a rate of around 3% of clients.

This might be fixed by bug 1596302

This might also be due to force closing

(In reply to Michael Droettboom [:mdroettboom] from comment #2)

This might also be due to force closing

Mh, maybe, yes.

I was also wondering if this could be due to the init path we get from a "4am trigger by the WorkManager". If we don't get an ON_START, we might be erroring out once we get an ON_STOP.

Depends on: 1602824
Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:backlog]

We still see a few of these from Fenix users, but since December, the percentage of affected clients on release channels have been below 1% of all clients. Over the last two months, less than 0.5% of clients are affected and seems to be slowly trending towards zero.

Is this worth still trying to figure out why we see this error, or can we close this?

(In reply to Travis Long [:travis_] from comment #4)

Is this worth still trying to figure out why we see this error, or can we close this?

< 1% is below our "this is a problem" treshold. I think it's fine to close and then reopen if we see this again.

Mike?

Flags: needinfo?(mdroettboom)

Yay. Let's close.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(mdroettboom)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.