s4:torture/rpc: move test_fsrvp_seq_timeout as last

test_fsrvp_seq_timeout may see share snapshots left-over, which can
cause problems if subsequent tests expect a clean slate
(i.e. enum_created).

Signed-off-by: David Disseldorp <ddiss@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>

diff --git a/source4/torture/rpc/fsrvp.c b/source4/torture/rpc/fsrvp.c
index 71750114a18622aad81c0b914eea13c77796328f..00e690de536dc5cb7c64c634e5bb99d557bb7ee0 100644 (file)
--- a/source4/torture/rpc/fsrvp.c
+++ b/source4/torture/rpc/fsrvp.c
@@ -945,8 +945,6 @@ struct torture_suite *torture_rpc_fsrvp(TALLOC_CTX *mem_ctx)
 
        torture_rpc_tcase_add_test(tcase, "share_sd",
                                   test_fsrvp_share_sd);
-       torture_rpc_tcase_add_test(tcase, "seq_timeout",
-                                  test_fsrvp_seq_timeout);
        torture_rpc_tcase_add_test(tcase, "enum_created",
                                   test_fsrvp_enum_created);
        torture_rpc_tcase_add_test(tcase, "sc_share_io",
@@ -963,6 +961,8 @@ struct torture_suite *torture_rpc_fsrvp(TALLOC_CTX *mem_ctx)
                                   test_fsrvp_get_version);
        torture_rpc_tcase_add_test(tcase, "is_path_supported",
                                   test_fsrvp_is_path_supported);
+       torture_rpc_tcase_add_test(tcase, "seq_timeout",
+                                  test_fsrvp_seq_timeout);
 
        return suite;
 }