On Mon, Aug 01, 2005 at 04:11:45PM -0400, John McCutchan wrote: > Yo, > > dnotify4.py is broken. The test creates a file, then watches it as a > directory, and expects to get a DELETED event. This is screwy. What > should happen is that the monitor fails.
it is the expected behaviour from the applications at this point. > > Also the flood tests are broken by design. They rely on very specific > timing information, which depending on system load can change. They worked fine until now on dnotify and inotify back-ends. They reflect potential application expectations. Maybe those are not reasonnable but if the test must be changed that need to be discussed beforehand not after the commit breaking them. Daniel -- Daniel Veillard | Red Hat Desktop team http://redhat.com/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ Gamin-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gamin-list
