-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add rclone tests to testsuite #90
Comments
We are testing rclone + current uplink against Stroj/Tardigrade backend so maybe gateway can also reuse existing rclone tests. One issue might be current problems with setting metadata as I think rclone tests are failing on that. https://github.com/storj/uplink/blob/main/testsuite/scripts/rclone.sh |
Current progress here: https://review.dev.storj.io/c/storj/gateway-mt/+/6430, and failures to be investigated: https://build.dev.storj.io/blue/organizations/jenkins/gateway-mt-gerrit/detail/gateway-mt-gerrit/3112/pipeline/ |
Change https://review.dev.storj.io/c/storj/gateway/+/6460 mentions this issue. |
Fixing storj/gateway-st#44 (https://review.dev.storj.io/c/storj/gateway/+/6431/15) was enough to fix some of the rclone tests, so here's a change to add rclone tests to ST: https://review.dev.storj.io/c/storj/gateway/+/6460. We can add these to MT later as well once we update the miniogw component. |
This is the same set up as uplink rclone tests except we are testing the s3 backend of rclone instead of the native Storj DC integration. Additionally, this disables the metainfo rate limiter for testing Gateway-ST, just as Gateway-MT currently does. rclone tests throw a lot of requests at the test Satellite, so we need to disable this. Updates storj/edge#90 Change-Id: I54462f14a251db562375025cf5faabf22ba86673
Change https://review.dev.storj.io/c/storj/gateway-mt/+/6529 mentions this issue. |
It seems a number of clients are actively using rclone, so I think it makes sense to write a few tests to make sure it's working correctly as part of our existing test suite scripts.
It's quite straightforward to get something going without a config file. Assuming same env vars we usually use:
The text was updated successfully, but these errors were encountered: