add dependency files and test logs to .gitignore

[vharron]

Summary

These files are generated as a part of the normal linux workflow and interfere with "git status"

[zturner]

Just curious, what are the .d files?

Also are the llgs log files generated by llgs? If so, aren't they using LLDB's built in logging infrastructure?

[vharron]

Just curious, what are the .d files?

Honestly I don't know. They just appear on my filesystem after a build/test. The files are empty.

test/lang/objc/self/main.d.39983

Also are the llgs log files generated by llgs? If so, aren't they using LLDB's built in logging infrastructure?

They are log files from test runs

test/tools/lldb-gdbserver/process-TestLldbGdbServer.LldbGdbServerTestCase.test_written_M_content_reads_back_correctly_llgs_dwarf.log

[zturner]

In theory this is a harmless change, so no reason to block it, but at the same time I'm not sure it's the right fix. I'm not really sure about the .d files, but with the log files, when running the test suite they usually go to lldb-test-traces which is out of tree since it's in the build directory.

What command are you using to run the test suite? Are you using ninja check-lldb? Or manually running dotest.py?

[vharron]

What command are you using to run the test suite?

ninja check-lldb

[zturner]

It sounds like there's a bug in either the test suite or the CMake target that calls into the test suite. I would rather have it fixed the right way, because I suspect it's probably a simple fix, would you mind trying to figure out what's going wrong? The relevant CMake target is in lldb/test/CMakeLists.txt at the very bottom (just dump the value of ${LLDB_DOSEP_ARGS} and re-generate), and the script itself is dosep.py and dotest.py. I think you can pass -v to them (through CMake) so they print verbose output. This makes it easy to debug them with log statements.

[apepper]

I think those log files are generated by llgs during testing when llgs local debugging is enabled.

• Alex

[zturner]

I'm not really knowledgeable about llgs, so if you guys think it's right go for it.

Ideally the solution (at least from the point of view of someone who doesn't know anything about llgs) is for the test suite to clean up the .d files (I believe it already cleans up other types of files, like executables, obj files, etc) so that it behaves like the rest of the test suite with regards to other files (for example, there's no gitignore rule for .out files, because the test suite cleans them up during make clean) and for the log files to go out of tree, but if you guys think that isn't possible or isn't feasible then that's fine.

.gitignore

 # Byte compiled python modules.
 *.pyc
 # vim swap files
 .*.swp
 .sw?
 # OS X specific files.
 .DS_store
 DerivedData/
+# dependency files
+*.d.*
+# test logs
+test/tools/lldb-gdbserver/*.log
 
 # Remote build configuration files.
 .remote-build.conf
 
 build/
 llvm-build/
 *xcuserdata
 xcshareddata/
 test/20*
 
 # We should ignore Xcode-style embedding of llvm/ at lldb root dir.
 /llvm/
 /DerivedData/
 /lldb.xcworkspace/xcshareddata/