Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.0.0, Lustre 1.8.6
-
None
-
3
-
5045
Description
sanity 171 in master could, and actually did for me, fail because of a race between the bash process executing test_171() and the background multiop process. By the time when test_171() returns, the multiop process could still be asleep. Test Framework would complain in run_one() about the existence of the multiop process, failing the subtest.
Another issue with this subtest is that the usage of multiop_bg_pause() is a little tricky. Since the subtest does specify any "_" for multiop, no "PAUSING" will be printed. As a result, the multiop_bg_pause() always fail after the "read -t 60 ...". An alternative implementation could be something like:
multiop $FILE Os & pid=$! ... wait $pid