redirecting output to a path that will work well on host or target.
copying file from output location to location on local host that
test will read from
Details
Diff Detail
Event Timeline
Uses remote working directory for stdout redirect.
Better chance of working on Windows.
test/types/AbstractBase.py | ||
---|---|---|
107 | You may use assertIsNotNone here. | |
107 | It should not be a big deal but it seems lldb.remote_platform_working_dir is considered to be a main root directory and lldb.remote_platform.GetWorkingDirectory is a single test root. So, lldb.remote_platform.GetWorkingDirectory() might be a slightly more fine-grained option here. | |
109 | s/process launch/platform process launch ? | |
189 | Could you extract this logic into a separate method to use it here and within generic_type_tester? |
test/types/AbstractBase.py | ||
---|---|---|
192 | Can you use os.path.join(lldb.remote_platform_working_dir, "lldb-stdout-redirect.txt") |
refactored process_launch_o into separate function
using os.path.join instead of string.format
using assertIsNotNone(
instead of assertNotEqual(None,
using lldb.remote_platform.GetWorkingDirectory()
instead of using lldb.remote_platform_working_dir
Would you mind doing the temp file changes too? It wasn't your code that
did it with hardcoded paths, but since you're in there anyway, maybe it's a
quick fix?
The one you removed then added back in the first and second patch set. It
was /tmp/golden_file.txt or something
I think because it was removed then added back. It was in the diff of diff
1 vs. diff 2. Anyway it's no big deal if it's not easy
Why we don't need mkdir.. put-file commands in non-debug configurations?