Closed Bug 1384381 Opened 3 years ago Closed 3 years ago
_privatebrowsing _placestitle .js | Uncaught exception - at browser _privatebrowsing _placestitle .js:48 - Type Error: null has no properties
Bug 1384381 - Intermittent failures in browser_privatebrowsing_placestitle.js and browser_privatebrowsing_placesTitleNoUpdate.js.
59 bytes, text/x-review-board-request
The problems here are due to concurrency, by the time we fetch the history details, looks like a transaction is still open and we read from an outdated db snapshot. We could try with some promiseAsyncUpdates() calls...
the failure rates here have been steady for the last 3 weeks, it looks like linux64-asan and linux64-ccov (which is a debug build, but instrumented for collecting code coverage). Given that we are seeing these on "artificial" configurations- should we skip this for those configurations, or plan on making the test more robust? ::mak, I see you had some suggestions about 4 weeks ago in Comment 1, is this something that could be done in the next week or two?
Whiteboard: [stockwell needswork]
keep in mind bug 1384130 has many failures in the same test.
I can have a look in the next days.
Assignee: nobody → mak77
Status: NEW → ASSIGNED
Priority: P5 → P1
Whiteboard: [stockwell needswork] → [stockwell needswork][fxsearch]
thanks for picking this up ::mak!
Comment on attachment 8902328 [details] Bug 1384381 - Intermittent failures in browser_privatebrowsing_placestitle.js and browser_privatebrowsing_placesTitleNoUpdate.js. https://reviewboard.mozilla.org/r/173868/#review179128
Attachment #8902328 - Flags: review?(standard8) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/fd00228df86b Intermittent failures in browser_privatebrowsing_placestitle.js and browser_privatebrowsing_placesTitleNoUpdate.js. r=standard8
Whiteboard: [stockwell fixed][fxsearch] → [stockwell fixed:timing][fxsearch]
You need to log in before you can comment on or make changes to this bug.