Perma browser_UsageTelemetry_urlbar.js | unexpected counts should be zero for FX_URLBAR_SELECTED_RESULT_INDEX at index 1 - 1 == 0 when Gecko 78 merges to Beta on 2020-06-01
Categories
(Firefox :: Address Bar, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox76 | --- | unaffected |
firefox77 | --- | unaffected |
firefox78 | + | verified |
People
(Reporter: aryx, Assigned: adw)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Log: https://treeherder.mozilla.org/logviewer.html#?job_id=303382464&repo=try
17:07:40 INFO - TEST-UNEXPECTED-FAIL | browser/modules/test/browser/browser_UsageTelemetry_urlbar.js | unexpected counts should be zero for FX_URLBAR_SELECTED_RESULT_INDEX at index 1 - 1 == 0 - JS frame :: resource://testing-common/TelemetryTestUtils.jsm :: assertHistogram :: line 297
4290 17:07:40 INFO - TEST-UNEXPECTED-FAIL | browser/modules/test/browser/browser_UsageTelemetry_urlbar.js | expected counts should match for FX_URLBAR_SELECTED_RESULT_INDEX at index 2 - 0 == 1 - JS frame :: resource://testing-common/TelemetryTestUtils.jsm :: assertHistogram :: line 291
4301 17:07:40 INFO - TEST-UNEXPECTED-FAIL | browser/modules/test/browser/browser_UsageTelemetry_urlbar.js | unexpected counts should be zero for FX_URLBAR_SELECTED_RESULT_INDEX_BY_TYPE_2 at index 1 - 1 == 0 - JS frame :: resource://testing-common/TelemetryTestUtils.jsm :: assertKeyedHistogramValue :: line 360
4306 17:07:40 INFO - TEST-UNEXPECTED-FAIL | browser/modules/test/browser/browser_UsageTelemetry_urlbar.js | expected counts should match for FX_URLBAR_SELECTED_RESULT_INDEX_BY_TYPE_2 at index 2 - 0 == 1 - JS frame :: resource://testing-common/TelemetryTestUtils.jsm :: assertKeyedHistogramValue :: line 354
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Hmm, this didn't happen on the simulation I ran in bug 1398416 comment 47. Maybe it's intermittent? Shouldn't be though... I'll take a look.
Assignee | ||
Comment 2•4 years ago
|
||
I think it's because the private search result is shown in Nightly but not otherwise. The test is failing because it expects the private search result to be at index 1 and the form history result to be at index 2, but the form history is actually at index 1. My simulation didn't catch it because it was still a Nightly build, so it still had the private search result. The test just needs to get the right index. There's another part of the test that clicks a remote suggestion, but it's not affected because the search happens to match a couple of history results, so the private search result isn't shown even on Nightly.
Assignee | ||
Comment 3•4 years ago
|
||
Assignee | ||
Comment 4•4 years ago
|
||
The private search result is shown in Nightly but not otherwise. The test is
failing because it expects the private search result to be at index 1 and the
form history result to be at index 2, but the form history is actually at index
- The test just needs to get the right index. There's another part of the test
that clicks a remote suggestion, but it's not affected because the search
happens to match a couple of history results, so the private search result isn't
shown even on Nightly.
Assignee | ||
Comment 5•4 years ago
|
||
Reporter | ||
Comment 6•4 years ago
|
||
Assignee | ||
Comment 7•4 years ago
|
||
Looks like it fixes it, thanks Sebastian.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 9•4 years ago
|
||
bugherder |
Reporter | ||
Comment 10•4 years ago
|
||
Verified fixed in yesterday's central-as-beta simulation: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=4071359fca65d9841bc50c2481ec9296463fb8a3
Updated•4 years ago
|
Description
•