-
-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sequester tmp directories #1987
Conversation
Interesting idea. I feel a little weird about committing a tmp dir though. @enebo? |
I'll take another look... I didn't look into generating the tmp dir as needed for some reason. |
I would almost prefer we just moved this to a build dir somewhere and probably leave them named as-is? Now that we use maven we no longer use build but having yet another scratch dir seems less appealing (even though it is more appealing than n tmp_* files). Also what is that .gitignore line for? |
the .gitignore is so that tmp dir gets saved to the repo. Moving the tmp_* directories to a build dir is equivalent for my purposes... I was just tired of having to manually delete them since they don't clean up properly with certain test failures. |
@tduehr Wow I did not notice that is tmp/.gitignore nor know you could have sub directory .gitignores!!! |
yup, the common idiom for keeping a directory around is either a .gitkeep file which does nothing but it's content and therefore can be tracked by git. Or add a .gitignore which has the added bonus of being able to keep the contents of the directory out of the repo without having to ignore the directory itself. Unsurprisingly .gitkeep has fallen out of favor. |
Has there been any decision on this one? |
I still don't like the idea of having |
I agree that would be better. |
* Use system-level temp location from Dir.mktmpdir. * Use FileUtils.rm_rf to delete directory in teardown. See #1987.
There was an additional problem with the test: it used |
Moves tmp_* directories under tmp/.