Wondering if anyone else has encountered/dealt with debugging lldb test failures like the one shown at the end of this email (“AssertionError: 10 != 5” in “test.assertEqual(process.GetState(), lldb.eStateStopped)” while checking that a breakpoint was reached)
Is there anything that could be done to improve the debuggability of such failures? Logging standard output/error from the lldb process or any other logging it might have? At least for one of these I managed to figure it out by running lldb directly on the binary and finding that the binary couldn’t find libc++.so (that’s a story for another bug/email thread, looks like maybe lldb libc++ pretty printer tests are using the system installed libc++, not the just-built libc++ (& thus not running if there is no system installed libc++)). But my current failure like this seems a bit more inscrutible and I’m still looking into it.
Looks like dotest.py has some sense of logging (it has a --log-success option which says preserves the logs even on failure - though the output of dotest.py, at least for me, has no mention of logs, log files, or where they might be located, and looking at the source points to some sort of “.log” files… ah, found some)
So, yeah, there do seem to be some Failure.log, SkippedTest.log, etc - should dotest print something about the paths to those files when it exits with failure, maybe?