labath added a comment. > I'm not sure if fixing this on a test-by-test basis is the right place for > it. It might be better to have dotest.py's run_suite() save the remote > platform and lldbtest.py's class Base setUpClass() method re-set the platform > before the test is invoked, in case it was mutated during a test run.
Yeah, I was thinking the same thing. I think that, at this point, we have enough tests needs things like this that a more general solution is justified. Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D66331/new/ https://reviews.llvm.org/D66331 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
