This is an archive of the discontinued LLVM Phabricator instance.

[NFC][llvm-reduce] Don't `rm -rf` in tests, `rm -f` is enough
AbandonedPublic

Authored by lebedev.ri on Jul 8 2020, 3:01 PM.

Diff Detail

Event Timeline

lebedev.ri created this revision.Jul 8 2020, 3:01 PM
nickdesaulniers accepted this revision.Jul 8 2020, 3:04 PM
This revision is now accepted and ready to land.Jul 8 2020, 3:04 PM
MaskRay accepted this revision.Jul 8 2020, 3:19 PM

Thanks!

If the test is writing the output file anyway - is the rm necessary? (lots of tests write to output files via "-o %t" from some tool or another and most don't delete %t before doing so)

If the test is writing the output file anyway - is the rm necessary? (lots of tests write to output files via "-o %t" from some tool or another and most don't delete %t before doing so)

They were added by you in rL372054, so indeed the revert of that commit would be the best solution now.

If the test is writing the output file anyway - is the rm necessary? (lots of tests write to output files via "-o %t" from some tool or another and most don't delete %t before doing so)

They were added by you in rL372054, so indeed the revert of that commit would be the best solution now.

Thought it might've been my fault :) great - removed in 8769611f0af2598177d8d03ad6dbbe064210bfed

lebedev.ri abandoned this revision.Jul 9 2020, 10:52 AM

If the test is writing the output file anyway - is the rm necessary? (lots of tests write to output files via "-o %t" from some tool or another and most don't delete %t before doing so)

They were added by you in rL372054, so indeed the revert of that commit would be the best solution now.

Thought it might've been my fault :) great - removed in 8769611f0af2598177d8d03ad6dbbe064210bfed

Thanks, that'll do.