Add "run_testserver --sync-test" for easy chromiumsync_test.py launching.

net/test/test_server_posix.cc

Index: net/test/test_server_posix.cc
diff --git a/net/test/test_server_posix.cc b/net/test/test_server_posix.cc
index f15acc3b84d0dfb30f32381a709c232caf2fb9d5..56b5ab50bb9ea779258cb6a01b5d378fb6ffa234 100644
--- a/net/test/test_server_posix.cc
+++ b/net/test/test_server_posix.cc
@@ -15,6 +15,7 @@
 #include "base/string_number_conversions.h"
 #include "base/string_util.h"
 #include "base/test/test_timeouts.h"
+#include "net/test/python_utils.h"
 
 namespace {
 
@@ -94,6 +95,8 @@ bool ReadData(int fd, ssize_t bytes_max, uint8* buffer,
 namespace net {
 
 bool TestServer::LaunchPython(const FilePath& testserver_path) {
+  VLOG(1) << "LaunchPython called with PYTHONPATH = " <<

[Paweł Hajdan Jr., 2012/03/13 17:15:23]

Is this needed?

[tim (not reviewing), 2012/03/15 00:41:40]

Fred asked for this in review, and I think it's useful in the event somebody
wants to run a nearby script (e.g. a test) in the same environment as the test
server, which is the problem we had that motivated this whole patch... I added a
comment.  

+          getenv(kPythonPathEnv);
   CommandLine python_command(FilePath(FILE_PATH_LITERAL("python")));
   python_command.AppendArgPath(testserver_path);
   if (!AddCommandLineArguments(&python_command))