clayborg added a comment. In D99497#2656502 <https://reviews.llvm.org/D99497#2656502>, @labath wrote:
> Isn't there a better way to ensure synchronization here? Maybe, executing > some command (setting a breakpoint, for instance), that will ensure that all > symbols have been parsed? That is what I attempted do in the test: set a breakpoint at 'main' which should trigger all of the needed events. Then we run to a breakpoint and hit it. and after we hit this breakpoint, then we check the progress events. One thing we could do to figure things out would be to dump the vscode.txt file for this test into the failing test. This would allow us to see what the packets looked like when a test fails. Is there a cleanup function or something we can do in the VS code tests that allows a test case to know it has an error and add some stuff to the test suite output?? CHANGES SINCE LAST ACTION https://reviews.llvm.org/D99497/new/ https://reviews.llvm.org/D99497 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
