Mozmill: random orange with closing the current tab but not properly waiting for message display completion

RESOLVED FIXED in Thunderbird 3.1b1

Status

defect
RESOLVED FIXED
10 years ago
9 years ago

People

(Reporter: rain1, Assigned: rain1)

Tracking

Trunk
Thunderbird 3.1b1
Dependency tree / graph

Thunderbird Tracking Flags

(thunderbird3.0 .5-fixed)

Details

Attachments

(1 attachment)

I've seen several failures of this kind on the tinderboxes.
Blocks: 540110
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).
Depends on: 545674
Depends on: 545727
Depends on: 545886
Posted patch patchSplinter Review
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+
http://hg.mozilla.org/comm-central/rev/1911acef7131
Status: ASSIGNED → RESOLVED
Closed: 10 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.