search for: run_target

...current '%run' solution works for full Canadian cross testing (i.e. run lit on BUILD, clang/llvm/whatever on HOST, and the tests themselves on TARGET, where {BUILD,HOST,TARGET} are all different machines). This use case is of particular interest to me. I suppose %run could be renamed %run_target, add %run_host, and then have an implied no-op %run_build on commands that don't have %run_target or %run_host. Perhaps someone might want to have BUILD be a different machine than where LIT runs, in which case %run_build would have to be explicit (but I'm not really interested in that u...

...works for >> full Canadian cross testing (i.e. run lit on BUILD, clang/llvm/whatever on >> HOST, and the tests themselves on TARGET, where {BUILD,HOST,TARGET} are all >> different machines). This use case is of particular interest to me. I >> suppose %run could be renamed %run_target, add %run_host, and then have an >> implied no-op %run_build on commands that don't have %run_target or >> %run_host. Perhaps someone might want to have BUILD be a different machine >> than where LIT runs, in which case %run_build would have to be explicit (but >> I'...

So I started prototyping remote testing for libcxx over the weekend: https://github.com/jroelofs/libcxx/tree/remote_test The SSHExecutor isn't quite finished yet, but this should give an idea of what I've got in mind. Does this look generic enough to work for other projects under the llvm-umbrella (LNT, test-suite, compiler_rt, libcxxabi, etc)? Are there use cases that you see