octoleo/s3fs-fuse
1
0
Fork 0
mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2024-06-02 00:50:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
511d223468
s3fs-fuse/test/small-integration-test.sh

31 lines
670 B
Bash
Raw Normal View History

add exit handler to cleanup on failures and other changes that make debugging easier
2015-03-09 17:33:47 +00:00
#!/bin/bash
Allow integration testing against Amazon S3 Example command line: S3FS_CREDENTIALS_FILE=keyfile \ TEST_BUCKET_1=somebucket \ S3PROXY_BINARY="" \ URL="http://s3.amazonaws.com" ./small-integration-test.sh
2015-09-11 08:25:37 +00:00
#
Integration test summary, continue on error Details in README.md and s3fs-integration-test-common.sh Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to add test suites besides small-integration-test.sh that can test with various s3fs options. Each test run starts in a uniquely named at the top of the bucket. This allows multiple runs against persistent storage without worrying about cleaning up in error conditions that leave artifiacts behind. Tests continues if a test case fails. Results are summarized at the end of the test run Environment variable to control debug level of s3fs-fuse Environment variable to enable public bucket (makes it easier to poke around with tools like curl) Environment variable to start s3fs-fuse under valgrind Environment variable that casues script sets up s3fs-fuse and then wait indefinitely, making it easy to experiment manually with the mount point. Additional test case
2016-02-05 12:24:13 +00:00
# Test s3fs-fuse file system operations with
Allow integration testing against Amazon S3 Example command line: S3FS_CREDENTIALS_FILE=keyfile \ TEST_BUCKET_1=somebucket \ S3PROXY_BINARY="" \ URL="http://s3.amazonaws.com" ./small-integration-test.sh
2015-09-11 08:25:37 +00:00
#
add exit handler to cleanup on failures and other changes that make debugging easier
2015-03-09 17:33:47 +00:00
set -o errexit
In preparation to remove the unnecessary "s3fs" directory from the trunk directory. First do a svn cp of all of the source up to trunk. This is supposed to preserve change history -- we'll see. The source remains untouched until this gets worked out. Also in preparation of bringing in the source collateral for the debian package into the repository. I expect that the top level will look like this: svn/ s3fs/ trunk/ tags/ branches/ dpkg/ trunk/ tags/ branches/ So far that's how it is looking. I'll be very careful to ensure integrity of the data. As a result this may be a multistep process. git-svn-id: http://s3fs.googlecode.com/svn/trunk@236 df820570-a93a-0410-bd06-b72b767a4274
2010-11-13 23:59:23 +00:00
# Require root
REQUIRE_ROOT=require-root.sh
fix rename before close nautilus does this when you drag and drop to overwrite a file: 1) create .goutputstream-XXXXXX to write to 2) fsync the fd for .goutputstream-XXXXXX 3) rename .goutputstream-XXXXXX to target file 4) close the fd for .goutputstream-XXXXXX previously, doing this on s3fs would result in an empty target file because after the rename, s3fs would not flush the content of .goutputstream-XXXXXX to target file. this change moves the FdEntity from the old path to the new path whenever rename happens. On flush s3fs would now flush the correct content to the rename target.
2015-01-12 22:46:24 +00:00
#source $REQUIRE_ROOT
add exit handler to cleanup on failures and other changes that make debugging easier
2015-03-09 17:33:47 +00:00
Integration test summary, continue on error Details in README.md and s3fs-integration-test-common.sh Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to add test suites besides small-integration-test.sh that can test with various s3fs options. Each test run starts in a uniquely named at the top of the bucket. This allows multiple runs against persistent storage without worrying about cleaning up in error conditions that leave artifiacts behind. Tests continues if a test case fails. Results are summarized at the end of the test run Environment variable to control debug level of s3fs-fuse Environment variable to enable public bucket (makes it easier to poke around with tools like curl) Environment variable to start s3fs-fuse under valgrind Environment variable that casues script sets up s3fs-fuse and then wait indefinitely, making it easy to experiment manually with the mount point. Additional test case
2016-02-05 12:24:13 +00:00
source integration-test-common.sh
add exit handler to cleanup on failures and other changes that make debugging easier
2015-03-09 17:33:47 +00:00
Integration test summary, continue on error Details in README.md and s3fs-integration-test-common.sh Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to add test suites besides small-integration-test.sh that can test with various s3fs options. Each test run starts in a uniquely named at the top of the bucket. This allows multiple runs against persistent storage without worrying about cleaning up in error conditions that leave artifiacts behind. Tests continues if a test case fails. Results are summarized at the end of the test run Environment variable to control debug level of s3fs-fuse Environment variable to enable public bucket (makes it easier to poke around with tools like curl) Environment variable to start s3fs-fuse under valgrind Environment variable that casues script sets up s3fs-fuse and then wait indefinitely, making it easy to experiment manually with the mount point. Additional test case
2016-02-05 12:24:13 +00:00
start_s3proxy
In preparation to remove the unnecessary "s3fs" directory from the trunk directory. First do a svn cp of all of the source up to trunk. This is supposed to preserve change history -- we'll see. The source remains untouched until this gets worked out. Also in preparation of bringing in the source collateral for the debian package into the repository. I expect that the top level will look like this: svn/ s3fs/ trunk/ tags/ branches/ dpkg/ trunk/ tags/ branches/ So far that's how it is looking. I'll be very careful to ensure integrity of the data. As a result this may be a multistep process. git-svn-id: http://s3fs.googlecode.com/svn/trunk@236 df820570-a93a-0410-bd06-b72b767a4274
2010-11-13 23:59:23 +00:00
Integration test summary, continue on error Details in README.md and s3fs-integration-test-common.sh Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to add test suites besides small-integration-test.sh that can test with various s3fs options. Each test run starts in a uniquely named at the top of the bucket. This allows multiple runs against persistent storage without worrying about cleaning up in error conditions that leave artifiacts behind. Tests continues if a test case fails. Results are summarized at the end of the test run Environment variable to control debug level of s3fs-fuse Environment variable to enable public bucket (makes it easier to poke around with tools like curl) Environment variable to start s3fs-fuse under valgrind Environment variable that casues script sets up s3fs-fuse and then wait indefinitely, making it easy to experiment manually with the mount point. Additional test case
2016-02-05 12:24:13 +00:00
#
# enable_content_md5
# Causes s3fs to validate file contents. This isn't included in the common
# options used by start_s3fs because tests may be performance tests
# singlepart_copy_limit
# Appeared in upstream s3fs-fuse tests, possibly a limitation of S3Proxy
# TODO: github archaeology to see why it was added.
#
start_s3fs -o enable_content_md5 \
-o singlepart_copy_limit=$((10 * 1024))
Restructing to take care of the directory rename. This is a checkpoint. No functional changes in this commit. git-svn-id: http://s3fs.googlecode.com/svn/trunk@288 df820570-a93a-0410-bd06-b72b767a4274
2010-12-20 05:26:27 +00:00
Integration test summary, continue on error Details in README.md and s3fs-integration-test-common.sh Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to add test suites besides small-integration-test.sh that can test with various s3fs options. Each test run starts in a uniquely named at the top of the bucket. This allows multiple runs against persistent storage without worrying about cleaning up in error conditions that leave artifiacts behind. Tests continues if a test case fails. Results are summarized at the end of the test run Environment variable to control debug level of s3fs-fuse Environment variable to enable public bucket (makes it easier to poke around with tools like curl) Environment variable to start s3fs-fuse under valgrind Environment variable that casues script sets up s3fs-fuse and then wait indefinitely, making it easy to experiment manually with the mount point. Additional test case
2016-02-05 12:24:13 +00:00
./integration-test-main.sh
Use s3proxy to run integration tests References #129.
2015-02-24 13:17:59 +00:00
Integration test summary, continue on error Details in README.md and s3fs-integration-test-common.sh Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to add test suites besides small-integration-test.sh that can test with various s3fs options. Each test run starts in a uniquely named at the top of the bucket. This allows multiple runs against persistent storage without worrying about cleaning up in error conditions that leave artifiacts behind. Tests continues if a test case fails. Results are summarized at the end of the test run Environment variable to control debug level of s3fs-fuse Environment variable to enable public bucket (makes it easier to poke around with tools like curl) Environment variable to start s3fs-fuse under valgrind Environment variable that casues script sets up s3fs-fuse and then wait indefinitely, making it easy to experiment manually with the mount point. Additional test case
2016-02-05 12:24:13 +00:00
echo "$0: tests complete."
Reference in New Issue Copy Permalink