baseline.duration errors still exist on glean-core
Categories
(Data Platform and Tools :: Glean: SDK, defect, P3)
Tracking
(Not tracked)
People
(Reporter: mdroettboom, Unassigned)
References
Details
(Whiteboard: [telemetry:glean-rs:backlog])
At a rate of around 3% of clients.
Comment 1•5 years ago
|
||
This might be fixed by bug 1596302
Reporter | ||
Comment 2•5 years ago
|
||
This might also be due to force closing
Comment 3•5 years ago
|
||
(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
.
Updated•5 years ago
|
Comment 4•5 years ago
|
||
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?
Comment 5•5 years ago
|
||
(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?
Reporter | ||
Comment 6•5 years ago
|
||
Yay. Let's close.
Description
•