Closed Bug 700657 Opened 13 years ago Closed 13 years ago

Permanent orange: TEST-UNEXPECTED-FAIL | test-instrument-setup.js | test_mail_account_setup

Categories

(Thunderbird :: Testing Infrastructure, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird 10.0

People

(Reporter: mconley, Assigned: mconley)

References

Details

Attachments

(1 file)

This just started showing up after Account Provisioner landed (bug 686347):

SUMMARY-UNEXPECTED-FAIL | test-instrument-setup.js | test_mail_account_setup
  EXCEPTION: Timed out waiting for window open!
    at: utils.js line 429
       TimeoutError("Timed out waiting for window open!") utils.js 429
       waitFor((function () this.monitorizeOpen()),"Timed out waiting for window open!",10000,100,[object Object]) utils.js 467
       WindowWatcher_waitForWindowOpen("mail:autoconfig") test-window-helpers.js 290
       wait_for_existing_window("mail:autoconfig") test-window-helpers.js 552
       test_mail_account_setup() test-instrument-setup.js 82
            frame.js 554
            frame.js 623
            frame.js 666
            frame.js 494
            frame.js 672
            server.js 182
            server.js 186

My working theory is that the Account Provisioner window is coming up instead of the Exiting Account dialog.  I'll know more in a few minutes.
Blocks: 686347
Assignee: nobody → mconley
Target Milestone: --- → Thunderbird 10.0
Attached patch Patch v1Splinter Review
So there were two bugs here:

The first was that the test was expecting the existing account dialog, but instead encountered the account provisioner window.  That's been fixed.

Next, some emailWizard code was using if (object.blah) to determine if exists as a key in object.  Instead, we need to use

"blah" in object

The test now passes for me reliably.
Attachment #572833 - Flags: review?(mbanner)
Attachment #572833 - Flags: review?(mbanner) → review+
Committed as http://hg.mozilla.org/comm-central/rev/b429f50bac8c
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.