Open Bug 517222 Opened 16 years ago Updated 3 years ago

xpcshell-tests: test_imapFilterActions.js fails intermittently on TB, take 2

Categories

(MailNews Core :: Filters, defect)

x86
All
defect

Tracking

(Not tracked)

People

(Reporter: sgautherie, Unassigned)

References

()

Details

(In reply to comment #0) { test_imapFilterActions.js | test failed (with xpcshell return code: 0), see following log: + test_imapFilterActions.js | [testCounts : 758] true == true test_imapFilterActions.js | 1 == 0 - See following stack: JS frame :: xpcshell/head.js :: do_throw :: line 197 JS frame :: xpcshell/head.js :: do_check_eq :: line 227 JS frame :: test_imapFilterActions.js :: testCounts :: line 759 JS frame :: test_imapFilterActions.js :: checkCopyToFolderBody :: line 300 JS frame :: test_imapFilterActions.js :: doTest :: line 479 + test_imapFilterActions.js | [folderCount : 686] 5 == 5 TEST-UNEXPECTED-FAIL | test_imapFilterActions.js | 4 == 5 - See following stack: JS frame :: xpcshell/head.js :: do_throw :: line 197 JS frame :: xpcshell/head.js :: do_check_eq :: line 227 JS frame :: test_imapFilterActions.js :: checkCopyToFolderBody :: line 302 JS frame :: test_imapFilterActions.js :: doTest :: line 479 }
I'm seeing similar things in my buffered io builds, which makes me nervous...
If you could give me a reliable way to reproduce this, even intermittently, I would be happy to work on it. What do you mean by a "buffered io build"? There is something odd going on with the imap unit tests generally. I backed out bug 531757 yesterday because it was failing 80% of the time in Linux builds. Not sure if the issue is real or a testing artifact, but I'd lay 80% odds it is a testing issue. Filtering is one of the toughest stresses on the system, so it ends up with a lot of these issus.
bienvenu, any feedback for comment 3? Is this OS=All, or mac-only?
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.