A first step for content process sandboxing on Windows.

Hi everyone, Patches have just landed on mozilla-inbound to turn on the content process sandbox on Windows by default. This means that anyone running on Windows with e10s enabled, will also be using the Chromium sandbox. The policy is only weak at the moment, to try and ensure that it doesn't b

Re: A first step for content process sandboxing on Windows.

on Windows is real. :) > > chris > > > On 11/29/14 2:03 PM, Bob Owen wrote: > > Hi everyone, > > > > Patches have just landed on mozilla-inbound to turn on the content process > > sandbox on Windows by default. > > This means that anyone running on

Re: PSA: MOZ_OVERRIDE and MOZ_FINAL are gone

On Sun, Mar 22, 2015 at 8:43 AM, wrote: > > Are the override and final keywords available only in Gecko 39 onwards, or can we assume that these keywords will work in earlier branches? > > For example, say I have a patch using these keywords that needs to be uplifted to Aurora or Beta, should I use

B2G Automation tests

All this talk of inbound bustage, reminded me of a problem I had a few weeks ago. I landed a change that was OK on try and inbound, but had actually introduced a serious bug for NUWA processes (sorry!). Over 24 hours later the problem was found by a B2G test run. I am not sure if this is purely au

PSA: On Windows, redirecting stdout & stderr to a file from mach commands that use python3 should now work

Hi, tl;dr: see subject For slightly more detail see: https://bugzilla.mozilla.org/show_bug.cgi?id=1648850 Probably the most relevant command using python3 is "mach run". Redirecting to a file is really useful for logging from sandboxed processes, because they can inherit file handles for stdout/