Use cmd.exe instead of python.exe for unit test.

base/process_util_unittest.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #define _CRT_SECURE_NO_WARNINGS
 
 #include <limits>
 
 #include "base/command_line.h"
 #include "base/debug/alias.h"
@@ skipping 396 matching lines @@
   EXPECT_TRUE(NULL != free_mem2.largest_ptr);
 }
 
 TEST_F(ProcessUtilTest, GetAppOutput) {
   // Let's create a decently long message.
   std::string message;
   for (int i = 0; i < 1025; i++) {  // 1025 so it does not end on a kilo-byte
                                     // boundary.
     message += "Hello!";
   }
+  // cmd.exe's echo always adds a \r\n to its output.
+  std::string expected(message);
+  expected += "\r\n";
 
-  FilePath python_runtime;
-  ASSERT_TRUE(PathService::Get(base::DIR_SOURCE_ROOT, &python_runtime));
-  python_runtime = python_runtime.Append(FILE_PATH_LITERAL("third_party"))
-                                 .Append(FILE_PATH_LITERAL("python_26"))
-                                 .Append(FILE_PATH_LITERAL("python.exe"));
-
-  CommandLine cmd_line(python_runtime);
-  cmd_line.AppendArg("-c");
-  cmd_line.AppendArg("import sys; sys.stdout.write('" + message + "');");
+  FilePath cmd(L"cmd.exe");
+  CommandLine cmd_line(cmd);
+  cmd_line.AppendArg("/c");
+  cmd_line.AppendArg("echo " + message + "");
   std::string output;
   ASSERT_TRUE(base::GetAppOutput(cmd_line, &output));
-  EXPECT_EQ(message, output);
+  EXPECT_EQ(expected, output);
 
   // Let's make sure stderr is ignored.
-  CommandLine other_cmd_line(python_runtime);
-  other_cmd_line.AppendArg("-c");
-  other_cmd_line.AppendArg("import sys; sys.stderr.write('Hello!');");
+  CommandLine other_cmd_line(cmd);
+  other_cmd_line.AppendArg("/c");
+  // http://msdn.microsoft.com/library/cc772622.aspx
+  cmd_line.AppendArg("echo " + message + " >&2");

[jar (doing other things), 2012/03/07 22:05:35]

Although a shell in cygwin or linux can handle things like ">&2" I don't think
that traditional DOS cmd can handle them.

Am I confused about what is being run here??

   output.clear();
   ASSERT_TRUE(base::GetAppOutput(other_cmd_line, &output));
   EXPECT_EQ("", output);
 }
 
 TEST_F(ProcessUtilTest, LaunchAsUser) {
   base::UserTokenHandle token;
   ASSERT_TRUE(OpenProcessToken(GetCurrentProcess(), TOKEN_ALL_ACCESS, &token));
   std::wstring cmdline =
       this->MakeCmdLine("SimpleChildProcess", false).GetCommandLineString();
@@ skipping 730 matching lines @@
       SetUpInDeathAssert();
       while ((value_ = base::AllocatePsychoticallyBigObjCObject())) {}
     }, "");
 }
 
 #endif  // !ARCH_CPU_64_BITS
 #endif  // OS_MACOSX
 
 #endif  // !defined(OS_ANDROID) && !defined(OS_OPENBSD) &&
         // !defined(OS_WIN) && !defined(ADDRESS_SANITIZER)