Closed Bug 1600958 Opened 6 years ago Closed 6 years ago

Perma TEST-UNEXPECTED-FAIL browser_aaa_eventTelemetry_run_first.js / browser_autocomplete_footer.js | Uncaught exception - waiting for telemetry event count of: 2 - timed out after 50 tries. when Gecko version increases to 74 on 06-01-20

Categories

(Firefox :: about:logins, defect, P1)

Product:
Firefox
Component:
about:logins
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
Firefox 73
Tracking Flags:
Tracking Status
firefox-esr68 --- unaffected
firefox71 --- unaffected
firefox72 --- unaffected
firefox73 + verified

People

(Reporter: malexandru, Assigned: sfoster)

References

Details

Attachments

(2 files)

Bug 1600958 - Don't expire the pwmgr.mgmt_interaction telemetry event probes. r?tdsmith,MattN
47 bytes, text/x-phabricator-request
Details | Review
Telemetry Data Review
3.67 KB, text/plain
tdsmith
: data-review+
Details

Central as Version Increase simulation: https://treeherder.mozilla.org/#/jobs?repo=try&selectedJob=279333875&resultStatus=success%2Ctestfailed%2Cbusted%2Cexception%2Cusercancel%2Crunnable&revision=56b228beb0397b584befffa42ee7feb4f919b035&searchStr=%28bc&group_state=expanded

Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=279333875&repo=try&lineNumber=3249

[task 2019-12-03T15:00:50.629Z] 15:00:50 INFO - runtests.py | Waiting for browser...
[task 2019-12-03T15:00:50.630Z] 15:00:50 INFO - GECKO(4041) | 1575385250624 Marionette DEBUG 1 <- [1,8,null,{"value":null}]
[task 2019-12-03T15:00:50.637Z] 15:00:50 INFO - GECKO(4041) | 1575385250632 Marionette DEBUG Closed connection 1
[task 2019-12-03T15:00:50.714Z] 15:00:50 INFO - *** Start BrowserChrome Test Results ***
[task 2019-12-03T15:00:50.769Z] 15:00:50 INFO - checking window state
[task 2019-12-03T15:00:50.794Z] 15:00:50 INFO - TEST-START | browser/components/aboutlogins/tests/browser/browser_aaa_eventTelemetry_run_first.js
[task 2019-12-03T15:00:53.452Z] 15:00:53 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:53.553Z] 15:00:53 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:53.654Z] 15:00:53 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:53.754Z] 15:00:53 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:53.855Z] 15:00:53 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:53.956Z] 15:00:53 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.056Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.157Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.258Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.358Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.459Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.560Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.660Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.761Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.861Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:54.962Z] 15:00:54 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.063Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.163Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.259Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.379Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.475Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.576Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.676Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.777Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.877Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:55.978Z] 15:00:55 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.079Z] 15:00:56 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.179Z] 15:00:56 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.280Z] 15:00:56 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.381Z] 15:00:56 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.481Z] 15:00:56 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.582Z] 15:00:56 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.683Z] 15:00:56 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.783Z] 15:00:56 INFO - GECKO(4041) | Waiting for 2 events, got 1
[task 2019-12-03T15:00:56.884Z] 15:00:56 INFO - TEST-INFO | started process screentopng
[task 2019-12-03T15:00:57.530Z] 15:00:57 INFO - TEST-INFO | screentopng: exit 0
[task 2019-12-03T15:00:57.531Z] 15:00:57 INFO - Buffered messages logged at 15:00:50
[task 2019-12-03T15:00:57.531Z] 15:00:57 INFO - Entering test bound setup
[task 2019-12-03T15:00:57.531Z] 15:00:57 INFO - Leaving test bound setup
[task 2019-12-03T15:00:57.532Z] 15:00:57 INFO - Entering test bound setup
[task 2019-12-03T15:00:57.532Z] 15:00:57 INFO - Buffered messages logged at 15:00:51
[task 2019-12-03T15:00:57.532Z] 15:00:57 INFO - Leaving test bound setup
[task 2019-12-03T15:00:57.533Z] 15:00:57 INFO - Entering test bound test_telemetry_events
[task 2019-12-03T15:00:57.533Z] 15:00:57 INFO - Buffered messages finished
[task 2019-12-03T15:00:57.533Z] 15:00:57 INFO - TEST-UNEXPECTED-FAIL | browser/components/aboutlogins/tests/browser/browser_aaa_eventTelemetry_run_first.js | Uncaught exception - waiting for telemetry event count of: 2 - timed out after 50 tries.
[task 2019-12-03T15:00:57.534Z] 15:00:57 INFO - Leaving test bound test_telemetry_events
[task 2019-12-03T15:00:57.534Z] 15:00:57 INFO - Console message: SENTINEL
[task 2019-12-03T15:00:57.535Z] 15:00:57 INFO - GECKO(4041) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2019-12-03T15:00:57.535Z] 15:00:57 INFO - GECKO(4041) | MEMORY STAT | vsize 2796MB | residentFast 307MB | heapAllocated 102MB
[task 2019-12-03T15:00:57.535Z] 15:00:57 INFO - TEST-OK | browser/components/aboutlogins/tests/browser/browser_aaa_eventTelemetry_run_first.js | took 6183ms

Matt, could you please take a look at this?

Flags: needinfo?(MattN+bmo)
Priority: -- → P1
Summary: Perma TEST-UNEXPECTED-FAIL browser_aaa_eventTelemetry_run_first.js | Uncaught exception - waiting for telemetry event count of: 2 - timed out after 50 tries. when Gecko version increases to 74 on 06-01-20 → Perma TEST-UNEXPECTED-FAIL browser_aaa_eventTelemetry_run_first.js / browser_autocomplete_footer.js | Uncaught exception - waiting for telemetry event count of: 2 - timed out after 50 tries. when Gecko version increases to 74 on 06-01-20
Assignee: nobody → sfoster
Attached file Telemetry Data Review —

This updates the data review from bug 1549115 to extend the recording of the pwmgr.mgmt_interaction collection of events to never expire. This was originally marked to expire at 74, but we now plan to monitor these interactions for the lifetime of this UI.

Attachment #9114315 - Flags: data-review?(chutten)
Comment on attachment 9114315 [details] Telemetry Data Review Load-balance to :tdsmith
Attachment #9114315 - Flags: data-review?(chutten) → data-review?(tdsmith)
Comment on attachment 9114315 [details] Telemetry Data Review Thanks! 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. This collection is Telemetry so is documented in its definitions file [Events.yaml](https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/Events.yaml) and the [Probe Dictionary](https://telemetry.mozilla.org/probe-dictionary/). Is there a control mechanism that allows the user to turn the data collection on and off? Yes. This collection is Telemetry so can be controlled through Firefox's Preferences. If the request is for permanent data collection, is there someone who will monitor the data over time? Yes. sfoster and loines will monitor. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 2, Interaction. Is the data collection request for default-on or default-off? Default on for all channels. Does the instrumentation include the addition of any new identifiers? 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? No, permanent collection.
Attachment #9114315 - Flags: data-review?(tdsmith) → data-review+
Attachment #9114313 - Attachment description: Bug 1600958 - Don't expire the pwmgr.mgmt_interaction telemetry event probes. r?chutten,MattN → Bug 1600958 - Don't expire the pwmgr.mgmt_interaction telemetry event probes. r?tdsmith,MattN
Flags: needinfo?(MattN+bmo)
Pushed by mozilla@noorenberghe.ca: https://hg.mozilla.org/integration/autoland/rev/21162f4a8ce1 Don't expire the pwmgr.mgmt_interaction telemetry event probes. r=MattN

https://hg.mozilla.org/mozilla-central/rev/21162f4a8ce1

Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox73: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: