Not sure if this is relevant, but I seem to recall the remote test
execution would spin off each test method run (test case level, not test
suite level) into a new directory. I don't think that would be inherently
broken by a no-clean scenario but we'd want to make sure it doesn't break.
-Todd
It is fairly common practice (at least it is for me) when figuring out why a
test failed, or adding to a test case, or when looking for a good example file
to poke at, etc, to go to some relevant test directory, do a make then poke
around a bunch. I don't generally remember to clean when I'm
While looking into a Windows-specific issue involving TestTargetAPI.py, I
noticed that we are building the exact same executable many times. Every
single test has a line such as self.buildDwarf() or self.buildDsym().
Those functions will first run make clean and then run make, essentially