Wait for Glean initialization in GleanDebugActivity
Categories
(Data Platform and Tools :: Glean: SDK, task, P1)
Tracking
(firefox108 unaffected, firefox109 unaffected, firefox110 wontfix, firefox111 fixed)
Tracking | Status | |
---|---|---|
firefox108 | --- | unaffected |
firefox109 | --- | unaffected |
firefox110 | --- | wontfix |
firefox111 | --- | fixed |
People
(Reporter: zmckenney, Assigned: janerik)
References
Details
(Whiteboard: [geckoview:m111?])
Attachments
(2 files)
Because of the current race condition for determining Glean.isInitialized()
in GleanDebugActivity, fenix tests now fail. Adding a wait with timeout will remove the race condition and ensure that tests are able to use Glean after initialization.
This is in relation to findings from this Bugzilla ticket 1808231, which fails due to changes in Fenix application initialization changes made in fenix pr 28350.
Assignee | ||
Comment 1•2 years ago
|
||
This blocks performance tests and we need to prioritize it. We need to get on this early next week.
Comment 2•2 years ago
•
|
||
Tracking for Fenix 111 because Dave Hunt says this Glean issue is causing a high number of failures (~50%) in Fenix performance tests in CI.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Assignee | ||
Comment 4•2 years ago
|
||
The PR is merged.
This requires a new Glean release. If bug 1805427 lands, I can get on that.
Until then I keep this bug open.
Assignee | ||
Comment 5•2 years ago
|
||
Depends on D167245
Comment 8•2 years ago
|
||
Relanded the push. The real culprit was a different push.
Comment 9•2 years ago
|
||
Backed out for causing build bustages complaining about Cargo and Glean.
Backout link: https://hg.mozilla.org/integration/autoland/rev/62c467a2a4d0d154a5abdf806dde1f052dc412cc
Failure log: https://treeherder.mozilla.org/logviewer?job_id=402989836&repo=autoland&lineNumber=359
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Description
•