Clang format slam.

net/test/python_utils.cc

Index: net/test/python_utils.cc
diff --git a/net/test/python_utils.cc b/net/test/python_utils.cc
index a67b2c129458896d2779d70eb404b8e17ba32a80..8b820bf44d8ac4588c6e8aa7e1041cc1de1be4ff 100644
--- a/net/test/python_utils.cc
+++ b/net/test/python_utils.cc
@@ -85,17 +85,16 @@ bool GetPyProtoPath(base::FilePath* dir) {
   // how far down it goes. So we walk upwards from DIR_EXE until we
   // find a likely looking spot.
   if (!TryRelativeToDir(generated_code_dir, kPyProto, dir)) {
-    LOG(WARNING) << "Can't find " << kPyProto.value()
-                 << " next to " << generated_code_dir.value();
+    LOG(WARNING) << "Can't find " << kPyProto.value() << " next to "
+                 << generated_code_dir.value();
     // On Chrome OS, we may have installed the test binaries and support tools
     // in a wholly separate location, relative to DIR_SOURCE_ROOT.  We'll want
     // to do a similar investigation from that point as well.
-    generated_code_dir = source_dir
-        .Append(FILE_PATH_LITERAL("out"))
-        .Append(FILE_PATH_LITERAL("Release"));
+    generated_code_dir = source_dir.Append(FILE_PATH_LITERAL("out"))
+                             .Append(FILE_PATH_LITERAL("Release"));
     if (!TryRelativeToDir(generated_code_dir, kPyProto, dir)) {
-      LOG(WARNING) << "Can't find " << kPyProto.value()
-                   << " next to " << generated_code_dir.value();
+      LOG(WARNING) << "Can't find " << kPyProto.value() << " next to "
+                   << generated_code_dir.value();
       return false;
     }
   }