Closed
Bug 1501295
Opened 6 years ago
Closed 6 years ago
Extend lifetime of FX_TAB_REMOTE_NAVIGATION_DELAY_MS probe.
Categories
(Core :: DOM: Content Processes, defect)
Core
DOM: Content Processes
Tracking
()
VERIFIED
FIXED
mozilla65
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox63 | --- | unaffected |
firefox64 | --- | unaffected |
firefox65 | + | verified |
People
(Reporter: ebalazs_, Assigned: mconley)
References
Details
Attachments
(2 files)
+++ This bug was initially created as a clone of Bug #1432482 +++ Central as beta: https://treeherder.mozilla.org/#/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception%2Cusercancel%2Crunnable&revision=44bfc9fea5dd3d3bfe732c22db62e14461553904&selectedJob=207244447 Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=207244447&repo=try&lineNumber=4711
Reporter | ||
Comment 1•6 years ago
|
||
mconley: Hi, This is a perma failure from today's version bump simulation. Can you have a look at this? Thank you!
status-firefox63:
--- → unaffected
status-firefox64:
--- → unaffected
status-firefox65:
--- → affected
status-firefox-esr60:
--- → unaffected
tracking-firefox65:
--- → ?
Flags: needinfo?(mconley)
Assignee | ||
Comment 2•6 years ago
|
||
This is because the FX_TAB_REMOTE_NAVIGATION_DELAY_MS probe maxes out at 65. Let's use this bug to track bumping the probe expiry.
Flags: needinfo?(mconley)
Summary: Perma browser_remote_navigation_delay_telemetry.js is going to permafail when the Gecko version number is bumped to 66 on 2018-12-10 → Extend lifetime of FX_TAB_REMOTE_NAVIGATION_DELAY_MS probe.
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Is there any ETA when this will get fixed (and thus the failure not show up anymore for version increase simulations)?
Assignee | ||
Comment 5•6 years ago
|
||
Attachment #9024028 -
Flags: review?(chutten)
Assignee | ||
Comment 6•6 years ago
|
||
Comment 7•6 years ago
|
||
Comment on attachment 9024028 [details]
data-review-form
Preliminary note:
There is no opt-in in release channel Firefox any more. (since Firefox 56 or so, IIRC). Extended collection is limited to nightly and beta (and aurora) by channel now, not preference.
DATA COLLECTION REVIEW RESPONSE:
Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?
Yes. Standard Telemetry mechanisms apply.
Is there a control mechanism that allows the user to turn the data collection on and off?
Yes. Standard Telemetry mechanisms apply.
If the request is for permanent data collection, is there someone who will monitor the data over time?
N/A, expires in Firefox 69.
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 2.
Is the data collection request for default-on or default-off?
Default on, prerelease channels only.
Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?
No.
Is the data collection covered by the existing Firefox privacy notice?
Yes.
Does there need to be a check-in in the future to determine whether to renew the data?
Yes. :mconley is responsible for renewing or removing the collection before it expires in Firefox 69.
---
Result: datareview+
Attachment #9024028 -
Flags: review?(chutten) → review+
Updated•6 years ago
|
Attachment #9024030 -
Attachment description: Bug 1501295 - Extend FX_TAB_REMOTE_NAVIGATION_DELAY_MS probe lifetime another 6 months. r?Gijs → Bug 1501295 - Extend FX_TAB_REMOTE_NAVIGATION_DELAY_MS probe lifetime another 6 months. data-review=chutten, r?Gijs
Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b0ebb63e720d Extend FX_TAB_REMOTE_NAVIGATION_DELAY_MS probe lifetime another 6 months. data-review=chutten, r=Gijs
Comment 9•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b0ebb63e720d
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
Comment 10•6 years ago
|
||
Verified fixed with yesterday's version increase simulation: https://treeherder.mozilla.org/#/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception%2Crunnable&revision=0fdc8b3d856f3abc380e354faa7fbb15fe0ec09c&group_state=expanded
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•