Closed Bug 545626 Opened 13 years ago Closed 13 years ago
Mozmill: random orange with closing the current tab but not properly waiting for message display completion
I've seen several failures of this kind on the tinderboxes.
I've got this tracked down, but I'm still seeing one timeout (which I think is being caused by a double message load by the persistence code).
This seems to not cause any timeouts once the patch in bug 545886 is applied.
Assignee: nobody → sid.bugzilla
Status: NEW → ASSIGNED
Attachment #426703 - Flags: review?(bugmail)
Attachment #426703 - Flags: review?(bugmail) → review+
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.1b1
Comment on attachment 426703 [details] [diff] [review] patch While this particular patch is npotb, this will cause timeouts unless all the patches it depends on lands, and some of those patches _are_ part of the build, and potentially risky. I think we should take this and suffer the timeouts on branch.
Attachment #426703 - Flags: approval-thunderbird3.0.3?
Attachment #426703 - Flags: approval-thunderbird3.0.3? → approval-thunderbird3.0.4?
Attachment #426703 - Flags: approval-thunderbird3.0.4? → approval-thunderbird3.0.5?
Comment on attachment 426703 [details] [diff] [review] patch Sid told me over irc that the timeouts in this case are just waitForxxx timeouts reaching their limit not timeouts as in random orange timeouts. Therefore a=Standard8 for 3.0 branch.
Attachment #426703 - Flags: approval-thunderbird3.0.5? → approval-thunderbird3.0.5+
Verifying test-only patch, I haven't seen this recently and the tests are generally green.
You need to log in before you can comment on or make changes to this bug.