I think this has been present since the pluggable store landing. Only happening on Windows: TEST-UNEXPECTED-FAIL | e:\buildbot\comm-central-win32-opt-unittest-xpcshell\build\xpcshell\tests\mailnews\imap\test\unit\test_largeOfflineStore.js | test failed (with xpcshell return code: 0), see following log: >>>>>>> TEST-INFO | (xpcshell/head.js) | test 1 pending Directory request for: SysD that we (mailDirService.js) are not handling, leaving it to another handler. Directory request for: MailD that we (mailDirService.js) are not handling, leaving it to another handler. Directory request for: MFCaF that we (mailDirService.js) are not handling, leaving it to another handler. Directory request for: DefRt that we (mailDirService.js) are not handling, leaving it to another handler. Directory request for: IMapMD that we (mailDirService.js) are not handling, leaving it to another handler. TEST-INFO | (xpcshell/head.js) | test 2 pending NEXT ERROR TEST-UNEXPECTED-FAIL | xpcshell/head.js | [Exception... "Component returned failure code: 0x80520010 (NS_ERROR_FILE_NO_DEVICE_SPACE) [nsIFileOutputStream.write]" nsresult: "0x80520010 (NS_ERROR_FILE_NO_DEVICE_SPACE)" location: "JS frame :: e:/buildbot/comm-central-win32-opt-unittest-xpcshell/build/xpcshell/tests/mailnews/imap/test/unit/test_largeOfflineStore.js :: run_test :: line 104" data: no] <<<<<<< If I look further up the log I see: 49.19 GB of space available As these are only unit test builds, I'd be surprised if we were filling up 45GB of space with the unit test.
I've never seen this on either of my windows machines. Maybe I need an older version of windows.
John: This appears to be an issue with the builders themselves. The tests are trying to write 2 and 4 GB files to the temp directories on the c drive (in c:\documents and settings\cltbld\local settings\temp iirc), however it appears those drives have now fallen to below 4GB in size. Can you take a look and see if there's stuff we can clean up?
Assignee: dbienvenu → nobody
Component: Backend → Release Engineering
Product: MailNews Core → Mozilla Messaging
QA Contact: backend → release
Version: Trunk → other
Ok, re-evaluating this, it doesn't happen on branches, which implies it isn't the buildbot slaves that are the issue. Also, I've gone back to when it started and it was definitely the pluggable store landing, there were no m-c changes at the time.
Component: Release Engineering → Backend
Product: Mozilla Messaging → MailNews Core
QA Contact: release → backend
Version: other → Trunk
Created attachment 588348 [details] [diff] [review] Proposed fix This seems to fix the test - on Windows. The issue appears to be that the default arguments to outputstream.init were for write-only, create if necessary and truncate. The truncate seems to have been messing with the file being marked as sparse. I don't know if all the tinderboxes loosing disk space coincided with the pluggable store landing (I think unlikely), but I don't quite know how to explain this otherwise. I've currently got a full set of platforms running on try with this fix (although it passed for me on tinderbox windows and debug build mac): http://build.mozillamessaging.com/tinderboxpushlog/?tree=ThunderbirdTry&rev=e16eee6f30bc
Assignee: nobody → mbanner
Status: NEW → ASSIGNED
Attachment #588348 - Flags: review?(dbienvenu)
Comment on attachment 588348 [details] [diff] [review] Proposed fix If this fixes it, great. But test_over2GBMailboxes doesn't use sparse files - only test_over4GBMailboxes.js and test_largeOfflineStores.js use mark_file_region_sparse. Perhaps we should make test_over2GBMailboxes use sparse files as well.
Attachment #588348 - Flags: review?(dbienvenu) → review+
SeaMonkey is affected too.
OS: Windows 2000 → Windows Server 2003
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 12.0
V.Fixed, per bug 718190 comment 0. (In reply to Mark Banner (:standard8) from comment #4) > I've currently got a full set of platforms running on try with this fix Fixed 1 of the 2 failures only :-| (+/- expected) (In reply to David :Bienvenu from comment #5) > Perhaps we should make test_over2GBMailboxes use sparse files as well. I filed bug 718190.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.