On Fri, Nov 9, 2012 at 5:01 AM, Gervase Markham g...@mozilla.org wrote:
On 09/11/12 08:50, Jonas Sicking wrote:
This is due to time constraints. It's much harder to implement in B2Gs
security model since we essentially don't have any chrome JS code
running other than what's part of gecko. In
On Mon, Nov 12, 2012 at 8:34 AM, Gervase Markham g...@mozilla.org wrote:
On 09/11/12 13:31, Robert Kaiser wrote:
There's no about: pages that run in chrome mode at all (which most do),
i.e. no about:config, about:crashes, about:memory, etc. - we cannot run
chrome-privileged pages inside
22 tests passed, 5 failed, 0 partial, 5 blockers
Smoketest Log:
https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdDRKOE1uanE3M3FtMDBOVjRIV253S1E#gid=36
Tests were performed with:
Gecko - 67437dc8dcbbc07dcd9c947c396ff997e0a98c80
Gaia - 92b7a950de3ec1cdecd90fb9d2cd7f930bb1f227
1 reboot,
Hi all,
Here is a baseline report for our first month of dogfooding focused on
stability and performance issues:
We have 1088 feedback posts from ~130 dogfooders in this first month Oct
13-Nov 13 with 12% of the posts being related to performance issues.
Of the 133 posts related to
