Closed Bug 1698771 Opened 4 years ago Closed 4 years ago

browser_PartnerLinkAttribution.js should wait for a rebuild event on the oneOffButtons instead of relying on the implicit initial TestUtils.waitForCondition timer

Categories

(Firefox :: Search, task)

task

Tracking

()

RESOLVED FIXED
88 Branch
Tracking Status
firefox88 --- fixed

People

(Reporter: florian, Assigned: florian)

References

Details

Attachments

(1 file)

browser_PartnerLinkAttribution.js becomes a perma fail on some platforms (specifically Windows 10 x64 opt) if I fix bug 1596165.

The error I get is:
TEST-UNEXPECTED-FAIL | browser/modules/test/browser/browser_PartnerLinkAttribution.js | Test timed out -
TEST-UNEXPECTED-FAIL | browser/modules/test/browser/browser_PartnerLinkAttribution.js | Found a tab after previous test timed out: https://example.com/?sourceId=Mozilla-search&search=searchbar -

Followed by this error for each of the tests that run afterwards:
A promise chain failed to handle a rejection: can't access property "isAppProvided", engine is null - stack: _updateURLBarPlaceholder@chrome://browser/content/browser.js:4071:9

Pushed by fqueze@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6dc3857184d6 browser_PartnerLinkAttribution.js should wait for a rebuild event on the oneOffButtons instead of relying on the implicit initial TestUtils.waitForCondition timer, r=Standard8.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: