Closed Bug 1145733 Opened 9 years ago Closed 8 years ago

Intermittent browser_fxa_login.js | Uncaught exception - 400: Bad Request

Categories

(Hello (Loop) :: Client, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Assigned: Mardak)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Pretty sure we've seen this a few times before and chalked it up to infra.

09:03:25 INFO - 1339 INFO going to retry
09:03:25 INFO - 1340 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | observer data should match expected data
09:03:25 INFO - 1341 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | observer data should match expected data
09:03:25 INFO - 1342 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | Shouldn't have a login error after
09:03:25 INFO - 1343 INFO Leaving test registrationWith401
09:03:25 INFO - 1344 INFO Entering test basicAuthorizationAndRegistration
09:03:25 INFO - 1345 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | observer data should match expected data
09:03:25 INFO - 1346 INFO registering
09:03:25 INFO - 1347 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | observer data should match expected data
09:03:25 INFO - 1348 INFO Console message: [JavaScript Error: "Error: Invariant Violation: forceUpdate(...): Can only force an update on mounted or mounting components." {file: "chrome://browser/content/loop/shared/libs/react-0.12.2.js" line: 18683}]
09:03:25 INFO - 1349 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | Guest should be displayed on the panel when not logged in
09:03:25 INFO - 1350 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | profile should be null before log-in
09:03:25 INFO - 1351 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | state of loop button should be empty when not logged in
09:03:25 INFO - 1352 INFO Login
09:03:25 INFO - 1353 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | observer data should match expected data
09:03:25 INFO - 1354 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | Check access_token
09:03:25 INFO - 1355 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | Check scope
09:03:25 INFO - 1356 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | Check token_type
09:03:25 INFO - 1357 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | email should exist in the profile data
09:03:25 INFO - 1358 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | uid should exist in the profile data
09:03:25 INFO - 1359 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | the email should be correct on the panel
09:03:25 INFO - 1360 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | state of loop button should be active when logged in
09:03:25 INFO - 1361 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | Check registered push URL
09:03:25 INFO - 1362 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | Check registered push URL
09:03:25 INFO - 1363 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | observer data should match expected data
09:03:25 INFO - 1364 INFO TEST-PASS | browser/components/loop/test/mochitest/browser_fxa_login.js | state of loop button should return to empty after panel is opened
09:03:25 INFO - 1365 INFO logout
09:03:25 INFO - 1366 INFO TEST-UNEXPECTED-FAIL | browser/components/loop/test/mochitest/browser_fxa_login.js | Uncaught exception - 400: Bad Request
[Mass Closure] Closing Intermittent as a one off
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
I think since this hasn't happened for several months it is fixed?
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
Since we don't know what fixed it, lets make it WFM.
Resolution: FIXED → WORKSFORME
I am getting this error intermittently while running mochitests, I'm thinking this is the same issue, therefore reopening bug:

The following tests failed:
690 INFO TEST-UNEXPECTED-FAIL | browser/extensions/loop/chrome/test/mochitest/browser_fxa_login.js | Check registered push URL - Got https://localhost/pushUrl/guest-rooms, expected https://localhost/pushUrl/fxa-rooms
Stack trace:
    chrome://mochikit/content/browser-test.js:test_is:967
    chrome://mochitests/content/browser/browser/extensions/loop/chrome/test/mochitest/browser_fxa_login.js:basicAuthorizationAndRegistration:325
    Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:937:23
    this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816:7
    Promise*this.PromiseWalker.scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:747:11
    this.PromiseWalker.schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:779:7
    this.PromiseWalker.completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:714:7
    TaskImpl_run@resource://gre/modules/Task.jsm:324:13
    promise callback*TaskImpl_handleResultValue@resource://gre/modules/Task.jsm:395:7
    TaskImpl_run@resource://gre/modules/Task.jsm:327:13
    Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:937:23
    this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816:7
    Promise*this.PromiseWalker.scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:747:11
    this.PromiseWalker.schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:779:7
    this.PromiseWalker.completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:714:7
    this.FxAccountsProfileClient.prototype._rawRequest/</request.onComplete@resource://gre/modules/FxAccountsProfileClient.jsm:163:18
    onStopRequest@resource://services-common/rest.js:499:5
691 INFO TEST-UNEXPECTED-FAIL | browser/extensions/loop/chrome/test/mochitest/browser_fxa_login.js | Uncaught exception - 400: Bad Request
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Might be related to the new bug 1266040.
Flags: needinfo?(edilee)
This or 1266040, whichever way you look at it, has been permaorange on WinXP debug since bug 1265865 landed a Loop update on the 19th.
Blocks: 1265865
The failing test basicAuthorizationAndRegistration wasn't able to run by itself for some timing issues. (Panel wasn't done rendering on "load".) This change makes it pass consistently when run the test file only has that one test:
https://hg.mozilla.org/try/rev/c260291a10ed2aa7a7c157f3e4eee549f3976486

But it's still failing xp debug https://treeherder.mozilla.org/#/jobs?repo=try&revision=af7875415277&selectedJob=19983119
Have you tried calling the new cleanupPanel() function from registerCleanupFunction in browser_copypanel.js? From what you're saying, that might help.
Flags: needinfo?(edilee)
Attachment #8745514 - Flags: review?(standard8)
Assignee: nobody → edilee
Blocks: 1266986
Blocks: 1266040
Comment on attachment 8745514 [details] [review]
[loop] Mardak:bug-1145733-intermittent > mozilla:master

Not tried it, but this looks good. r=Standard8
Attachment #8745514 - Flags: review?(standard8) → review+
https://github.com/mozilla/loop/commit/dda4594f71380c2acaa4669bc7d23339574188b7

Standard8, how should we land this on m-c?
Flags: needinfo?(standard8)
Blocks: 1267835
Landed via bug 1267835 https://hg.mozilla.org/integration/fx-team/rev/b567617d9f02
Status: REOPENED → RESOLVED
Closed: 9 years ago8 years ago
Flags: needinfo?(standard8)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: