Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Subject: debug parallel root checks
Date: Fri, 9 Mar 2018 15:47:40 +0100	[thread overview]
Message-ID: <201803091547.40271.sweet_f_a@gmx.de> (raw)

Hi,

Our parallel root checks look already nice on the first view.
On the second view they fail the stress test, at least on my
system.

Mostly umounting fails due to "device in use" and similar. For me it
seems that "udevadm --settle" has no effect sometimes. Very often the
label, utab, context and recursive mount tests make problems. I've made
sure that udisks and similar devils are not running.

One may try to use my script sippet below to run a loop until it fails.
You should remove the "sort" from run.sh to get more failures:

patch tests/run.sh
-----
 printf "%s\n" ${comps[*]} |
-       sort |
        xargs -I '{}' -P $paraller_jobs -n 1 bash -c "'{}' \"$OPTS\" ||
                echo 1 >> $top_builddir/tests/failures"
-----



#### ultest.bash ###
## Attention, using sudo"

i=0
while true; do
    echo -e "\n#### run test loop: $((++i)) ####\n"

    ## select any interesting subset of all tests and shuffle
    mytests=$(git grep -l "^ts_skip_nonroot$" -- tests/ts/*/ \
                | sort --random-sort | sed "s@tests/ts/@@")
    test -n "$mytests" || { echo "empty tests!?"; break; }

    time sudo ./tests/run.sh --parallel=30 --exclude="some-bad-tests" $mytests \
        || break
done

echo -e "\n#### bad run: $i ####\n"

###############


cu,
Rudi

             reply	other threads:[~2018-03-09 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 14:47 Ruediger Meier [this message]
2018-03-09 15:06 ` debug parallel root checks Ruediger Meier
2018-03-09 21:46   ` Karel Zak
2018-03-09 22:16     ` Ruediger Meier
2018-03-09 21:48   ` Karel Zak
2018-03-09 22:28     ` Ruediger Meier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201803091547.40271.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox