generic/620: fix order of require_scratch calls
authorDarrick J. Wong <djwong@kernel.org>
Wed, 14 Apr 2021 01:05:14 +0000 (18:05 -0700)
committerEryu Guan <guaneryu@gmail.com>
Sun, 18 Apr 2021 12:53:53 +0000 (20:53 +0800)
commita2330d65ff55893907d63cda7d2ce0aedfb8e6bb
tree2ff0358b76e169aaff8a70de5ad3392c9021c553
parent552a0cdd65d0635e02e041f451afb2eebe1f006b
generic/620: fix order of require_scratch calls

_require_scratch_16T_support does not itself check that the scratch
device exists, which means that it depends on someone else to call
_require_scratch.  Document this dependency and fix this test so that we
can run:

./check --exact-order generic/374 generic/620

on an ext4 filesystem without g/620 tripping over the mess left by g/374
when it calls _notrun.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
common/rc
tests/generic/620