newtab-content ping going to be broken in 157
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr153 | --- | unaffected |
| firefox157 | --- | unaffected |
| firefox158 | --- | wontfix |
| firefox159 | --- | fixed |
People
(Reporter: thecount, Assigned: thecount)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [hnt])
Attachments
(1 external file)
Bug 2070362 landed some new telemetry, and had some protection for trainhops that was targeting 157, but actually missed 157 by hours, and ended up in 158.
So now the trainhopped code is going to send these events into 157, but the metrics yamls are not up to date, and it's going to reject the ping.
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
| Assignee | ||
Comment 1•1 month ago
|
||
Comment 2•1 month ago
|
||
Set release status flags based on info from the regressing bug 2070362
Comment 4•1 month ago
|
||
| bugherder | ||
Comment 5•1 month ago
|
||
The patch landed in nightly and beta is affected.
:thecount, please make an uplift decision for beta:
- For beta, nominate the patch for beta uplift approval if the fix should be included in this release, or set
status-firefox158towontfixif the fix can wait for the next release.
See Requesting an Uplift for documentation on how to request an uplift.
For more information, please visit BugBot documentation.
Comment 6•1 month ago
|
||
This was fixed with a trainhop that went out to everyone last week. We did see the expected spike in Glean errors, and the drop-off as the trainhop has saturated. I don't think we need to uplift anything here for next weeks release.
Updated•1 month ago
|
Description
•