Comments on: inotify support for autotest http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/ It looks like my blog Wed, 17 Mar 2010 07:10:29 +0000 http://wordpress.org/?v=2.6.3 By: autotest-inotify: extend autotest to use inotify - Duplo http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-590 autotest-inotify: extend autotest to use inotify - Duplo Thu, 11 Feb 2010 22:35:36 +0000 http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-590 [...] on autotest-fsevent, which extends autotest to use Mac OS X’s FSEvents system, as well as Alban Peignier’s work using libinotify and the INotify gem. Where autotest-inotify differs from Schwyn’s work, is [...] [...] on autotest-fsevent, which extends autotest to use Mac OS X’s FSEvents system, as well as Alban Peignier’s work using libinotify and the INotify gem. Where autotest-inotify differs from Schwyn’s work, is [...]

]]> By: Ryan Davis http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-232 Ryan Davis Wed, 23 Apr 2008 07:23:12 +0000 http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-232 If you're running high CPU on autotest, you either have too much crap in your project and/or you're not excluding enough in your .autotest. I won't be touching inotify or any other platform specific hacks. If you’re running high CPU on autotest, you either have too much crap in your project and/or you’re not excluding enough in your .autotest.

I won’t be touching inotify or any other platform specific hacks.

]]> By: she http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-228 she Wed, 27 Feb 2008 13:09:18 +0000 http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-228 Are there really bugs in ruby-inotify? I am a bit unsure now, would be nice if you could explain what is the problem Are there really bugs in ruby-inotify?

I am a bit unsure now, would be nice if you could explain what is the problem

]]> By: joe http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-225 joe Tue, 22 Jan 2008 01:00:33 +0000 http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-225 What bugs did you run into with ruby-inotify? You solution requires that /dev/inotify exist, and that doesn't exist on my system (I heard that it got phased out, something about inotifyfs)... I also ran across RInotify which i haven't tried yet: http://rubyforge.org/projects/rinotify/ anyways, I wrote a little script with ruby-inotify and it's been working ok to monitor directory changes for the last 15 minutes or so, just curious what I have to watch out for. What bugs did you run into with ruby-inotify? You solution requires that /dev/inotify exist, and that doesn’t exist on my system (I heard that it got phased out, something about inotifyfs)… I also ran across RInotify which i haven’t tried yet: http://rubyforge.org/projects/rinotify/

anyways, I wrote a little script with ruby-inotify and it’s been working ok to monitor directory changes for the last 15 minutes or so, just curious what I have to watch out for.

]]> By: Scott Nedderman http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-221 Scott Nedderman Sun, 06 Jan 2008 01:22:18 +0000 http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-221 I ran into this problem too with a packed vendor directory and the rspec_on_rails plugin. Here's my solution: http://blog.netphase.com/2008/01/05/autotest-cpu-fix/ I ran into this problem too with a packed vendor directory and the rspec_on_rails plugin. Here’s my solution: http://blog.netphase.com/2008/01/05/autotest-cpu-fix/

]]> By: Ryan Davis http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-215 Ryan Davis Wed, 19 Dec 2007 11:20:57 +0000 http://blog.tryphon.org/alban/archives/2007/10/26/inotify-support-for-autotest/#comment-215 I dunno what lappy you're running on, but it ran very light on my 12" pb (1.2Mhz PPC G4?). autotest's file scan runs proportional to the number of files in the directory tree it starts in (obviously) minus the files you tell it to exclude. If you're doing rails development and have a way packed vendor dir, add vendor to the exclusions regexp (it'll be a much cleaner process in the next release of zentest) and you should see a drop in CPU. I dunno what lappy you’re running on, but it ran very light on my 12″ pb (1.2Mhz PPC G4?).

autotest’s file scan runs proportional to the number of files in the directory tree it starts in (obviously) minus the files you tell it to exclude.

If you’re doing rails development and have a way packed vendor dir, add vendor to the exclusions regexp (it’ll be a much cleaner process in the next release of zentest) and you should see a drop in CPU.

]]>