Re: [lldb-dev] How do I use lit to only run the lldb test suite, now that dotest multiprocessing capabilities have been removed?

Thanks for the pointers, Jonas. I cloned a new repo, then ran cmake, setting up arbitrary test compiler and lldb locations. Then ran llvm-lit tools/lldb/lit/Suite , and the test suite ran as expected. There were a few failures, but I've got a plan now. Ted > -Original Message- > From:

Re: [lldb-dev] How do I use lit to only run the lldb test suite, now that dotest multiprocessing capabilities have been removed?

So far the only thing that changed by removing multiprocess is that `--no-multiprocess` is always enabled. Everything else you describe is still possible, and will continue to be possible. Even when we remove the driver functionality from dotest.py this will all continue to work. The only

Re: [lldb-dev] How do I use lit to only run the lldb test suite, now that dotest multiprocessing capabilities have been removed?

Hi Jonas, What I need is a way to run the test suite with arbitrary command line arguments. Sometimes I want to run one or more tests with -f, sometimes I want to run one or more test files with -p, and sometimes I want to run the entire suite, either in parallel or 1 at a time

Re: [lldb-dev] How do I use lit to only run the lldb test suite, now that dotest multiprocessing capabilities have been removed?

Hey Ted, On Thu, Aug 8, 2019 at 2:08 PM Ted Woodward wrote: > > Thanks Jonas. > > Is full support for --param fairly recent? I tried it with a version of our > master, based on top-of-tree from about a month ago, and it didn't work quite > right. It's passing the dotest args, but it's also

Re: [lldb-dev] How do I use lit to only run the lldb test suite, now that dotest multiprocessing capabilities have been removed?

Thanks Jonas. Is full support for --param fairly recent? I tried it with a version of our master, based on top-of-tree from about a month ago, and it didn't work quite right. It's passing the dotest args, but it's also generating some args, so I'm seeing odd effects. Here is my run line:

Re: [lldb-dev] How do I use lit to only run the lldb test suite, now that dotest multiprocessing capabilities have been removed?

Is this in the on-line docs somewhere? Jim > On Aug 8, 2019, at 12:49 PM, Jonas Devlieghere via lldb-dev > wrote: > > Hey Ted, > > 1. You can run just the dotest-tests by pointing lit at the > `lit/Suite` directory. > 2. You can pass arguments to dotest by passing `dotest-args` in --param.

Re: [lldb-dev] How do I use lit to only run the lldb test suite, now that dotest multiprocessing capabilities have been removed?

Hey Ted, 1. You can run just the dotest-tests by pointing lit at the `lit/Suite` directory. 2. You can pass arguments to dotest by passing `dotest-args` in --param. The invocation would look something like this: /path/to/llvm/bin/llvm-lit /path/to/lldb/lit/Suite --param 'dotest-args=--foo

[lldb-dev] How do I use lit to only run the lldb test suite, now that dotest multiprocessing capabilities have been removed?

RE: https://reviews.llvm.org/D65311 Internally we use dotest to run the lldb test suite with various RTOS configurations for the test binaries. In these runs we don't care about the lit tests or the unit tests, because they are OS agnostic. We do this by specifying the compiler, lldb, and test