What happened?
The LARGE_BINARY test uploads a real object to the configured S3 bucket on every S3-reachable run and never deletes it. The suite teardown removes only the local fixture files, so each run leaves another orphaned object under objects// in the bucket. The test should clean up what it uploaded. Found during post-merge review of #7800; still live on main.
How to reproduce?
Run the LARGE_BINARY tests in FileScanSourceOpExecSpec with S3 reachable (s3LargeBinariesBucket configured). After the run, list the bucket prefix objects// — the uploaded object is still there.
Version/Branch
1.4.0-incubating-SNAPSHOT (main)
Commit Hash (Optional)
70bd3b3
What happened?
The LARGE_BINARY test uploads a real object to the configured S3 bucket on every S3-reachable run and never deletes it. The suite teardown removes only the local fixture files, so each run leaves another orphaned object under objects// in the bucket. The test should clean up what it uploaded. Found during post-merge review of #7800; still live on main.
How to reproduce?
Run the LARGE_BINARY tests in FileScanSourceOpExecSpec with S3 reachable (s3LargeBinariesBucket configured). After the run, list the bucket prefix objects// — the uploaded object is still there.
Version/Branch
1.4.0-incubating-SNAPSHOT (main)
Commit Hash (Optional)
70bd3b3