Skip to content
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

Flaky tests result while testing against Digital Ocean backend #1989

Open
phoebusm opened this issue Nov 5, 2024 · 1 comment
Open

Flaky tests result while testing against Digital Ocean backend #1989

phoebusm opened this issue Nov 5, 2024 · 1 comment
Labels
flaky test Tracking tests that fail inconsistently in CI

Comments

@phoebusm
Copy link
Collaborator

phoebusm commented Nov 5, 2024

  1. Incorrect XML result returned after calling delete
  • Extra 0 at the end
[DEBUG] 2024-10-25 03:05:12.852 CURL [140287207695936] (DataIn) 64
<?xml version="1.0" encoding="UTF-8"?><DeleteResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
0 
  • Raised to their support
  1. Cannot find host...
  • Not 100% sure but plausibly due to their rate limit
  • Cannot repeat once lowering the IO threads setting
  • Their rate limit indeed looks lower than AWS:
DO:
Rate Limits
All Spaces buckets have the following request rate limits:

1500 requests (any operation) per IP address per second to all buckets on an account
10 concurrent PUT or COPY requests to any individual object in a bucket

AWS:
... For example, you can send 3,500 PUT/COPY/POST/DELETE or 5,500 GET/HEAD requests per second per partitioned Amazon S3 prefix.
@phoebusm phoebusm added the flaky test Tracking tests that fail inconsistently in CI label Nov 5, 2024
@phoebusm
Copy link
Collaborator Author

phoebusm commented Nov 5, 2024

Parked as no user is requiring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky test Tracking tests that fail inconsistently in CI
Projects
None yet
Development

No branches or pull requests

2 participants