check-lldb-lit should just be a dependency of check-lldb, so the dotest.py tests should still run.
Are one of the lit tests failing? That might explain why subsequent tests aren't run. vedant > On Feb 23, 2018, at 4:13 PM, Adrian McCarthy <amcca...@google.com> wrote: > > As of this afternoon, it seems ninja check-lldb runs only the lit tests and > not the dotest.py tests. Was this an intentional change? > > On Fri, Feb 23, 2018 at 3:36 PM, Vedant Kumar via lldb-dev > <email@example.com <mailto:firstname.lastname@example.org>> wrote: > Cool, I'll work up a patch for this. > > And thanks for commenting on PR36494, I'm testing a fix out right now :). > > vedant > >> On Feb 23, 2018, at 3:35 PM, Pavel Labath <lab...@google.com >> <mailto:lab...@google.com>> wrote: >> >> On 23 February 2018 at 15:17, Vedant Kumar <v...@apple.com >> <mailto:v...@apple.com>> wrote: >>> Second, TestClient::SendMessage is generating quite a lot of "INFO" output >>> which clutters up the terminal. Pavel, would you mind if I removed this >>> logging? >>> >> >> Yeah, we should probably do that. The idea here was that the packet >> log would provide you with additional context for the situation when >> the test fails, but it *is* very verbose. I'll have to come up with a >> better solution for error reporting here. > > > _______________________________________________ > lldb-dev mailing list > email@example.com <mailto:firstname.lastname@example.org> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > <http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev> > >
_______________________________________________ lldb-dev mailing list email@example.com http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev