Closed Bug 936426 Opened 7 years ago Closed 5 years ago

Intermittent browser_social_activation.js | waitForProviderLoad: provider profile was not set

Categories

(Firefox Graveyard :: SocialAPI, defect)

x86
macOS
defect
Not set

Tracking

(firefox37 wontfix, firefox38 fixed, firefox38.0.5 fixed, firefox39 fixed, firefox40 fixed, firefox-esr31 unaffected, firefox-esr38 fixed)

RESOLVED FIXED
Firefox 40
Tracking Status
firefox37 --- wontfix
firefox38 --- fixed
firefox38.0.5 --- fixed
firefox39 --- fixed
firefox40 --- fixed
firefox-esr31 --- unaffected
firefox-esr38 --- fixed

People

(Reporter: cbook, Assigned: mixedpuppy)

References

()

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound opt test mochitest-browser-chrome on 2013-11-08 02:48:29 PST for push ca17e1dd094c

slave: talos-r4-snow-073

https://tbpl.mozilla.org/php/getParsedLog.php?id=30323285&tree=Mozilla-Inbound

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/social/browser_social_activation.js | waitForProviderLoad: provider profile was not set
Summary: Intermittent TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/social/browser_social_activation.js | waitForProviderLoad: provider profile was not set → Intermittent browser_social_activation.js | waitForProviderLoad: provider profile was not set
Attached patch fix intermittentSplinter Review
seems to fix this.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=0cbef3503038

This removes the worker since it wasn't necessary for this test, but I think the actual fix is checking gBrowser.contentDocument before accessing location.
Assignee: nobody → mixedpuppy
Attachment #8600235 - Flags: review?(mhammond)
Attachment #8600235 - Flags: review?(mhammond) → review+
https://hg.mozilla.org/mozilla-central/rev/b2a3462b18e3
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 40
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.