On Mon, Jan 20, 2014 at 12:04 AM, Thomas Rast <t...@thomasrast.ch> wrote:
> Nguyễn Thái Ngọc Duy <pclo...@gmail.com> writes:
>> This can be used to force watcher on when running the test
>> git-file-watcher processes are not automatically cleaned up after each
>> test. So after running the test suite you'll be left with plenty
>> git-file-watcher processes that should all end after about a minute.
> Probably not a very good idea, especially in noninteractive use? E.g.,
> a bisection through the test suite or parallel test runs on different
> commits may exhaust the available processes and/or memory.
I think we run out of inotify resources before hitting process/memory
limits. At least that's the case when running tests in parallel.
> Each test should make an effort to clean up all watchers before
For now it's hard to do this correctly. Maybe once we get the
multi-repo file watcher, we could launch one watcher per trash
directory and cleaning up would be easier.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html