From 53feebcccb2bb2758c5790a938bb03e2948af63c Mon Sep 17 00:00:00 2001
From: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Date: Thu, 30 Jan 2014 18:09:32 +0100
Subject: <chromium> Remove the Running without renderer sandbox error message

We are currently not planing to enable the sandbox and the error
pollutes the auto tests output.

Reviewed-by: Andras Becsi <andras.becsi@digia.com>
Change-Id: I2675aa2e03394f1c03e4df6bd1b21764ed19206a
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
---
 chromium/content/renderer/renderer_main.cc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/chromium/content/renderer/renderer_main.cc b/chromium/content/renderer/renderer_main.cc
index 63c72ae934b..f0c16d27815 100644
--- a/chromium/content/renderer/renderer_main.cc
+++ b/chromium/content/renderer/renderer_main.cc
@@ -223,7 +223,6 @@ int RendererMain(const MainFunctionParams& parameters) {
     if (!no_sandbox) {
       run_loop = platform.EnableSandbox();
     } else {
-      LOG(ERROR) << "Running without renderer sandbox";
 #ifndef NDEBUG
       // For convenience, we print the stack trace for crashes. We can't get
       // symbols when the sandbox is enabled, so only try when the sandbox is
-- 
cgit v1.2.1