(split out from https://bugzilla.mozilla.org/show_bug.cgi?id=1749276#c65) The `browser_archive.js` test deletes (archives) a thread, then clicks "undo". It then waits until it sees an item appear in back the thread tree. Buuuuut... if you augment the test to have more messages in the thread, the undo (really a message copy) operation is still running when the test end conditions are met (at least one message has been re-instated, but the rest are still in-progress). The test then ends, and the test cleanup code is run. And the cleanup code deletes the account being used for the test - which includes the incomingserver and its msgStore. So... kaboom! https://searchfox.org/comm-central/source/mail/base/test/browser/browser_archive.js#93 It _seems_ to run OK as is - maybe with 2 messages it completes quickly enough that the timing doesn't become an issue? In any case, I think it'd be worth seeing if that test can be changed to ensure all the messages have been copied back before finishing the test. The line in question is: https://searchfox.org/comm-central/source/mail/base/test/browser/browser_archive.js#93 It seems like this'd be a prime candidate for an intermittent failure.
Bug 1852480 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(split out from https://bugzilla.mozilla.org/show_bug.cgi?id=1749276#c65) The `browser_archive.js` test deletes (archives) a thread, then clicks "undo". It then waits until it sees an item appear in back the thread tree. Buuuuut... if you augment the test to have more messages in the thread, the undo (really a message copy) operation is still running when the test end conditions are met (at least one message has been re-instated, but the rest are still in-progress). The test then ends, and the test cleanup code is run. And the cleanup code deletes the account being used for the test - which includes the incomingserver and its msgStore. So... kaboom! The line which checks for the reappearance of the messages is: https://searchfox.org/comm-central/source/mail/base/test/browser/browser_archive.js#93 To increase the number of messages in the thread, change the '2's here into '5's, say: https://searchfox.org/comm-central/source/mail/base/test/browser/browser_archive.js#50 Doing this causes the test to crash. It _seems_ to run OK as is - maybe with 2 messages it completes quickly enough that the timing doesn't become an issue? In any case, I think it'd be worth seeing if that test can be changed to ensure all the messages have been copied back before finishing the test. It seems like this'd be a prime candidate for an intermittent failure.