summaryrefslogtreecommitdiff
path: root/source3/script
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2020-03-13 15:45:16 -0700
committerJeremy Allison <jra@samba.org>2020-03-18 18:03:28 +0000
commit566658d914176c41942e3c6aba404ae369aeb123 (patch)
treeb45853c829aacdf3b676871ff3c3005f21fc622b /source3/script
parent319c93f0c6a949545229b616dfbd4f51baf11171 (diff)
downloadsamba-566658d914176c41942e3c6aba404ae369aeb123.tar.gz
s3: tests: Slight tweak to the force-close share test.
Turns out on a fast desktop machine 10MB is too small, and by the time we've done the 'sleep 1' to make sure the smbclient got scheduled and started processing the 'put' command, it's already done. Tweak the file size to be 20MB from 10MB. 10MB seems to work reliably on gitlab-ci and on sn-devel, but making the put size 20MB makes sure it's still in flight when we force-close the share, even on a fast desktop box. 20MB shouldn't be too burdonsome even on ci VM's. BUG: https://bugzilla.samba.org/show_bug.cgi?id=14301 Signed-off-by: Jeremy Allison <jra@samba.org> Reviewed-by: Ralph Boehme <slow@samba.org>
Diffstat (limited to 'source3/script')
-rwxr-xr-xsource3/script/tests/test_force_close_share.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/source3/script/tests/test_force_close_share.sh b/source3/script/tests/test_force_close_share.sh
index ebfff5af77c..da78b5a752e 100755
--- a/source3/script/tests/test_force_close_share.sh
+++ b/source3/script/tests/test_force_close_share.sh
@@ -32,7 +32,7 @@ mkfifo smbclient-stdin smbclient-stdout smbclient-stderr
# Create a large-ish testfile
rm testfile
-head -c 10MB /dev/zero >testfile
+head -c 20MB /dev/zero >testfile
CLI_FORCE_INTERACTIVE=1; export CLI_FORCE_INTERACTIVE