tests: (lslcoks) insert a sleep between taking a lock and running lslocks

Close #2624.

It appears that there is a time lag between locking and its visibility
in /proc/locks.  See the unstbale results of errors I observed in
https://github.com/util-linux/util-linux/pull/2629.

Signed-off-by: Masatake YAMATO <yamato@redhat.com>

diff --git a/tests/ts/lslocks/lslocks b/tests/ts/lslocks/lslocks
index a9ef69a35ed41a8e41c1f6ebfae1dc7b8279ab65..912fac83bb62550c630db78c9ce7626e58facc25 100755 (executable)
--- a/tests/ts/lslocks/lslocks
+++ b/tests/ts/lslocks/lslocks
@@ -53,6 +53,14 @@ OFD_METHODS=(
     lease-w
 )
 
+SLEEP()
+{
+    # It appears that there is a time lag between locking and its
+    # visibility in /proc/locks.  See the unstbale results of errors I
+    # observed in https://github.com/util-linux/util-linux/pull/2629.
+    sleep 1
+}
+
 DFD=18
 COLS_WITH_HOLDERS=COMMAND,TYPE,SIZE,MODE,START,END,HOLDERS
 run_lslocks()
@@ -63,6 +71,8 @@ run_lslocks()
        rm -f "${FILE}"
        coproc MKFDS { "$TS_HELPER_MKFDS" make-regular-file $FD file="$FILE" lock=$m; }
        if read -r -u "${MKFDS[0]}" PID; then
+           SLEEP
+
            "$TS_CMD_LSLOCKS" ${OPTS} --pid "${PID}" -o "${COLS}"
            echo "# $m + ${COLS} + ${OPTS}": $?
            "$TS_CMD_LSLOCKS" ${OPTS} --pid "${PID}" -o PATH | sed -e 's#.*\('"$FILE0"'\)--[0-9]\+ *$#\1#'
@@ -81,6 +91,7 @@ run_lslocks_with_co_holders()
     {
        rm -f "${FILE}"
        coproc MKFDS { "$TS_HELPER_MKFDS" make-regular-file $FD file="$FILE" lock=$m dupfd=$DFD; }
+       SLEEP
        if read -r -u "${MKFDS[0]}" PID; then
            "$TS_CMD_LSLOCKS" ${OPTS} --pid "${PID}" -o "${COLS_WITH_HOLDERS}" | sed -e "s/${PID},/1,/g"
            echo "# $m + ${COLS_WITH_HOLDERS} + ${OPTS}": ${PIPESTATUS[0]}