Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
This issue was created by maloo for Andreas Dilger <adilger@whamcloud.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/eb05239e-d305-491c-96d9-11c435f42e7c
test_21d failed with the following error:
multiop still running
This "multiop still running" message was only printed for the one subtest, and didn't cause any failures in any later subtests (even though it is checked at the end of every subtest, so it appears to have been a transient issue, caused by running a second "multiop" in the background and not waiting for it to exit before the test is finished.
If this becomes a regular occurrence, it needs a small change to add a wait for the second mutliop:
$MULTIOP $DIR/$tdir-2/f Oc &
pid2=$!
sleep 1
:
rm -rf $DIR/$tdir-*
wait $pid2 || true
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
recovery-small test_21d - multiop still running