Closed
Bug 1677701
Opened 4 years ago
Closed 4 years ago
Update glean-core and enable rkv safe-mode migration
Categories
(Toolkit :: Telemetry, task, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
85 Branch
People
(Reporter: janerik, Assigned: janerik)
References
Details
(Whiteboard: [telemetry:fog:m6])
Attachments
(1 file)
|
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
We need to land an update of glean-core and then enable the rvk-safe-mode feature.
| Assignee | ||
Comment 1•4 years ago
|
||
Pushed by jrediger@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b87ca4c75bec
Update glean-core to v33.4.0 and enable safe-mode. r=Dexter
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox85:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
| Assignee | ||
Comment 4•4 years ago
|
||
Comment on attachment 9188264 [details]
Bug 1677701 - Update glean-core to v33.4.0 and enable safe-mode. r?dexter!
Beta/Release Uplift Approval Request
- User impact if declined: Crashes such as those in bug 1538541
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): The underlying rkv database code is already used by m-c and works just fine.
The usage here has automated tests in Glean. Additionally it's driving our data collection and we validate that the incoming data looks correct. - String changes made/needed:
Attachment #9188264 -
Flags: approval-mozilla-beta?
Comment 5•4 years ago
|
||
Comment on attachment 9188264 [details]
Bug 1677701 - Update glean-core to v33.4.0 and enable safe-mode. r?dexter!
Topcrash fix. Approved for 84.0b4.
Attachment #9188264 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 6•4 years ago
|
||
| bugherder uplift | ||
status-firefox84:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•