[Lldb-commits] [lldb] r358213 - [test] Disable CommandScriptImmediateOutputFile on Windows

[Jonas Devlieghere via lldb-commits]

Author: jdevlieghere
Date: Thu Apr 11 12:18:40 2019
New Revision: 358213

URL: http://llvm.org/viewvc/llvm-project?rev=358213&view=rev
Log:
[test] Disable CommandScriptImmediateOutputFile on Windows

Somehow the path gets messed up. The command looks correct, but the
python path is not.

(lldb) mywrite
E:\build_slave\lldb-x64-windows-ninja\build\tools\lldb\lit\Commands\
  CommandScriptImmediateOutput\Output\
  CommandScriptImmediateOutputFile.test.tmp.read.txt r

No such file or directory:
'E:build_slavelldb-x64-windows-ninjabuildtoolslldblitCommands
  CommandScriptImmediateOutputOutput
  CommandScriptImmediateOutputFile.test.tmp.read.txt'

Maybe the shlex module is escaping it?

Modified:
    lldb/trunk/lit/Commands/CommandScriptImmediateOutput/CommandScriptImmediateOutputFile.test

Modified: lldb/trunk/lit/Commands/CommandScriptImmediateOutput/CommandScriptImmediateOutputFile.test
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/lit/Commands/CommandScriptImmediateOutput/CommandScriptImmediateOutputFile.test?rev=358213&r1=358212&r2=358213&view=diff
==============================================================================
--- lldb/trunk/lit/Commands/CommandScriptImmediateOutput/CommandScriptImmediateOutputFile.test (original)
+++ lldb/trunk/lit/Commands/CommandScriptImmediateOutput/CommandScriptImmediateOutputFile.test Thu Apr 11 12:18:40 2019
@@ -1,3 +1,5 @@
+# UNSUPPORTED: system-windows
+
 # Test that LLDB correctly allows scripted commands to set immediate output to
 # a file.