Open Bug 1717130 Opened 3 years ago Updated 3 years ago

mailnews/search/test/unit/test_quarantineFilterMove.js fails when default store is maildir

Categories

(MailNews Core :: Backend, defect)

defect

Tracking

(Not tracked)

People

(Reporter: benc, Unassigned)

References

(Blocks 1 open bug)

Details

There's some discussion over in Bug 1044456 that implies this test is irrelevant under maildir... but I'm not sure. Still looking into it. If that is the case, it needs to handle maildir anyway (even if that's just to skip or bail out early).

Works fine when mbox is the default store type, but under maildir it just hangs while waiting for a 'msgsClassified' notification.

To replicate, switch to maildir as default. In mailnews.js:

-pref("mail.serverDefaultStoreContractID", "@mozilla.org/msgstore/berkeleystore;1");
+pref("mail.serverDefaultStoreContractID", "@mozilla.org/msgstore/maildirstore;1");

and run the test:

$ ./mach xpcshell-test comm/mailnews/search/test/unit/test_quarantineFilterMove.js
See Also: → 1717147

Yes it irrelevant for maildir. What could it do there?
The idea behind quarantining is to don't get the hole folder nuked by AV just because an evil message arrived. For maildir, it's just going to remove the single message so no problem.

(In reply to Magnus Melin [:mkmelin] from comment #1)

Yes it irrelevant for maildir. What could it do there?

It could run without failing :-)
This test doesn't do anything quarantine-specific, it just turns on quarantining and does a fairly basic filter test. So the fact it fails on maildir seems to be indicative of something more serious.
(but yeah - when we change to maildir as default I'd want to make sure this test is still run over an mbox store).

You need to log in before you can comment on or make changes to this bug.