Closed Bug 554611 Opened 15 years ago Closed 12 years ago

Intermittent sessionstore/test/browser_248970_a.js | file should be created after setting interval to 0

Categories

(Firefox :: Session Restore, defect)

Product:
Firefox
Component:
Session Restore
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: asuth, Unassigned)

References

Details

(Keywords: intermittent-failure)

I am declaring this an intermittent problem because the only way "file should be created after setting interval to 0" gets reported, thanks to the guards in the file, is if this (correct) sequence of events happens: - (the decision to write the file is made because of the preference event, this ends up in saveStateDelayed which calls saveState which calls _saveStateObject which calls _writeFile) - sss_writeFile's call to NetUtil.asyncCopy completes, invoking the provided callback function that invokes Components.isSuccessCode(rc) to verify success, and only then calls Services.obs.notifyObservers on "sessionstore-state-write-complete" - waitForFileExistence's observer gets called... - getSessionstoreFile().exists() returns false. In other words, this error message looks like the very definition of a race on checking for the existence of a file because the callback is only going to get called if the stream copier declares victory. Links to the interesting code: http://mxr.mozilla.org/mozilla-central/source/browser/components/sessionstore/src/nsSessionStore.js#2965 http://mxr.mozilla.org/mozilla-central/source/browser/components/sessionstore/test/browser/browser_248970_a.js#68 http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1269422946.1269423987.24267.gz WINNT 5.2 mozilla-central opt test mochitest-other on 2010/03/24 02:29:06 TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/components/sessionstore/test/browser/browser_248970_a.js | file should be created after setting interval to 0 TEST-INFO | chrome://mochikit/content/browser/browser/components/sessionstore/test/browser/browser_248970_a.js | Console message: [JavaScript Error: "uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIFile.remove]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://mochikit/content/browser/browser/components/sessionstore/test/browser/browser_248970_a.js :: anonymous :: line 98" data: no]"] TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/components/sessionstore/test/browser/browser_248970_a.js | Timed out TEST-INFO | checking window state
er, and this happened on my Win Opt Mochitest "oth" run, but did not happen on the Win Debug Mochitest "oth" run. Both (Opt + Debug) Mochitest "oth" runs for Windows ran green for the 2 pushes following mine, further bolstering my assertion that this is not my fault.
Blocks: 438871
Whiteboard: [orange]
Summary: bizarre likely intermittent failure in browser_248970_a.js | file should be created after setting interval to 0 → Intermittent sessionstore/test/browser_248970_a.js | file should be created after setting interval to 0
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of: {random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open} There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.