Followup question, many months later:
--build-and-test mode apparently considers the entire subdirectory’s set of tests to be a single ‘test’. This is not at all unreasonable, of course, but our use of it has turned up some suboptimal behavior that I haven’t found a workaround for.
In our case, we have a subproject being invoked this way that runs a number of benchmarks as part of its “test”, which can take a loooooong time if you don’t have your system configured correctly (leading some users to assume there is a hang). In fact, progress is being made, it’s just that (1) all the tests and benchmarks in the subdir are running serially and must all complete, and (2) there doesn’t appear to be any way to get build-and-test mode to emit output from the sub-test to the enclosing test (at least, nothing I’ve found) until it completes.
In my ideal world, there would be some way for
--build-and-test to have the sub-tests participate in the enclosing test command (ie, with the same granularity in terms of parallelism, timeouts, etc); I’m going to guess that this is unlikely, but I’ll ask anyway just in case there’s a hidden option I’ve missed.
Failing that, is there at least some way to get --build-and-test to flush test output periodically, so that there’s indication that something is happening?