Files
seaweedfs/test/s3/snowflake
Chris LuandClaude Opus 5.5 2089abecf3 ci: cache Snowflake suite Maven deps and fall back to a Central mirror (#12763)
* ci: cache the Snowflake suite's Maven dependencies under their own key

setup-java's maven cache key hashes the repository pom.xml files, which
other Java workflows share. The Snowflake job restored that cache, which
lacks the suite's plugins and dependencies, and never saved its own because
the key already existed. Every run downloaded the whole suite dependency
tree from Maven Central and failed when Central answered 429.

Key the cache on run.sh, which pins the suite revision.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* ci: fall back to Google's Maven Central mirror in the Snowflake job

A cold cache still resolves about 36 MB of plugins and dependencies, and
Maven gives up after three 429 retries within 30 s. Add the mirror as a
settings-profile repository; Maven tries it first and moves on to Central
for any artifact the mirror fails to serve.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 00:00:41 -08:00
..

Snowflake S3Compat API test suite

Integration tests that run the upstream Snowflake s3compat API test suite against SeaweedFS. The suite covers getBucketLocation, getObject (including range reads), getObjectMetadata, putObject (including a 5 GB upload), listObjectsV2 (including paged listing of >1000 objects), deleteObject, deleteObjects, copyObject, and generatePresignedUrl.

Running locally

Requires weed (or WEED_BIN), the aws CLI, mvn, and JDK 11+ on PATH.

(cd weed && go install -buildvcs=false)   # build weed first
bash test/s3/snowflake/run.sh

run.sh starts a weed server with S3 enabled, calls prepare.sh to create the fixtures, clones the suite into a scratch dir, and runs mvn -Dtest=S3CompatApiTest. Set WORK_DIR to keep the server log and suite clone around, SKIP_SERVER_START=1 with ENDPOINT_URL to run against an already-running server, and see the top of run.sh for the other overrides.

Notes

  • The server runs with -s3.autoCreateBucket=false so PUTs to a missing bucket return NoSuchBucket like AWS; the suite asserts this.
  • The suite forces virtual-hosted-style bucket addressing, which requires wildcard DNS that does not exist for a local endpoint. run.sh switches it to path-style access with a sed patch.
  • NOT_ACCESSIBLE_BUCKET is a real bucket carrying a deny-all bucket policy, which is how the suite's AccessDenied negative tests are satisfied.
  • CI runs Maven with maven-settings.xml, which adds Google's Maven Central mirror in front of Central, so a 429 from one falls through to the other. Locally, pass it with MAVEN_ARGS="-s $PWD/test/s3/snowflake/maven-settings.xml".