bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: inotify back end for tail -f on linux


From: Jim Meyering
Subject: Re: inotify back end for tail -f on linux
Date: Sun, 07 Jun 2009 18:20:54 +0200

Giuseppe Scrivano wrote:
> The new version includes all these changes.

Please merge this into your changes:

diff --git a/tests/Makefile.am b/tests/Makefile.am
index c108356..e4c7f22 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -137,6 +137,7 @@ TESTS =                                             \
   misc/date-next-dow                           \
   misc/ptx-overrun                             \
   misc/xstrtol                                 \
+  tail-2/wait                                  \
   misc/od                                      \
   misc/mktemp                                  \
   misc/arch                                    \
@@ -243,6 +244,7 @@ TESTS =                                             \
   misc/unexpand                                        \
   misc/uniq                                    \
   misc/xattr                                   \
+  tail-2/pid                                   \
   chmod/c-option                               \
   chmod/equal-x                                        \
   chmod/equals                                 \
@@ -419,8 +421,6 @@ TESTS =                                             \
   tail-2/big-4gb                               \
   tail-2/proc-ksyms                            \
   tail-2/start-middle                          \
-  tail-2/pid                                   \
-  tail-2/wait                                  \
   touch/dangling-symlink                       \
   touch/dir-1                                  \
   touch/fail-diag                              \

Why?
Because the two new tests were started late enough
that they could make a parallel "make check" take longer.
Here's a comment from tests/Makefile.am:

  # Put tests that sleep early, but not all together, so in parallel builds
  # they share time with tests that burn CPU, not with others that sleep.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]