[llvm-dev] Status of debuginfo-tests

[Zachary Turner via llvm-dev]

On Thu, Sep 7, 2017 at 11:40 AM David Blaikie <dblaikie at gmail.com> wrote:

> On Thu, Sep 7, 2017 at 11:34 AM Zachary Turner <zturner at google.com> wrote:
>
>> Even if it were under llvm, that doesn't mean it would have to be part of
>> ninja check-all.  Currently we have lldb/test and lldb/unittests, what
>> about a third lldb/dbgtests?  Then you could run it as ninja check-dbgtest.
>>
>
> Having them in lldb seems like an interesting question - not sure what the
> value is in having them in a separate repo compared to having them in the
> LLDB project. (I mean, long term, I think LLDB testing should probably have
> fewer of these end-to-end tests (ideally few tests that actually run a
> compiler/execute a resulting program (avoiding that so the tests are more
> portable, reliable, etc)) - but it's reasonable to have some & probably OK
> that they live in the LLDB repo (for LLVM these sort of tests live
> separately in the test-suite repo)
>
> Maybe because it makes the tests more likely to be run, more reliable (so
> they don't fail due to LLDB changes - makes it easier for Clang/llvm
> developers to act on regressions, etc)
>

Sorry, I had a bad typo.  I meant we have llvm/test, llvm/unittests, so
what about llvm/dbgtests.

I definitely woudln't want them in LLDB, as my entire motivation is to
write tests against a non-LLDB debugger.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170907/f3b35d14/attachment-0001.html>