[llvm] r326710 - Fuzzer: remove temporary files after we're done with them.

[Tim Northover via llvm-commits]

Hmm, possibly a race in Windows deigning to allow us to remove our temporaries since the exact failure point varies. Interestingly “rm” is only used about 15 times without “-f” in the tests (as opposed to >200 as a whole), and most of those within a directory we’ve just created.

So in the absence of any actual Windows experience, I’ll try adding “-f” as a pot-shot.

Tim.

> On 9 Mar 2018, at 15:23, Hans Wennborg <hans at chromium.org> wrote:
> This is breaking on one of the buildbots, e.g.
> http://lab.llvm.org:8011/builders/clang-x64-ninja-win7/builds/9300
> 
> On Mon, Mar 5, 2018 at 4:49 PM, Tim Northover via llvm-commits
> <llvm-commits at lists.llvm.org> wrote:
>> Author: tnorthover
>> Date: Mon Mar  5 07:49:00 2018
>> New Revision: 326710
>> 
>> URL: http://llvm.org/viewvc/llvm-project?rev=326710&view=rev
>> Log:
>> Fuzzer: remove temporary files after we're done with them.
>> 
>> These were just copies of the relevant fuzzer binary with (presumably)
>> meaningful suffixes, but accounted for more than 10% of my build
>> directory (> 8GB). Hard drive space is cheap, but not that cheap.
>> 
>> Modified:
>>    llvm/trunk/test/tools/llvm-isel-fuzzer/aarch64-execname-options.ll
>>    llvm/trunk/test/tools/llvm-isel-fuzzer/execname-options.ll
>>    llvm/trunk/test/tools/llvm-opt-fuzzer/exec-options.ll