binwiederhier b259872393 Collect s3 test objects left behind by runs that died ...

A per-run key space stops concurrent runs from deleting each other's objects,
but it also means nothing ever revisits the keys of a run that was killed
before its cleanup, so those leak forever. The fixed prefix this replaced at
least swept itself on the next run.

The first test to construct an s3 store now sweeps the shared test root once
per binary, deleting anything older than two hours: a test takes seconds and a
CI job minutes, so nothing that old can belong to a live run. Failures to list
or delete are logged, not fatal, since this is hygiene and not the test.

The age filter is a pure function with its own tests, including that an object
whose modification time could not be read is left alone rather than treated as
infinitely old.

This is a backstop. A lifecycle rule on the bucket (expire testpkg-* after a
day) is the real fix, since it also covers a bucket nobody runs tests against
for a while and cannot be skipped by a crash.

2026-10-07 00:34:19 +00:00

..

backend_file.go

More consistent logging

2026-03-22 08:38:41 -04:00

backend_s3.go

Fix brittle tests, move delete batching into client package, run s3 tests against real bucket

2026-03-22 15:10:28 -04:00

backend.go

Allow streaming to S3

2026-03-21 21:14:49 -04:00

store_file_test.go

Fixes

2026-03-25 15:28:23 -04:00

store_s3_test.go

Collect s3 test objects left behind by runs that died

2026-10-07 00:34:19 +00:00

store_test.go

Refine sync() to properly update sizes

2026-03-23 12:44:40 -04:00

store.go

Disable HTTP2 for S3 backend with ?disable_http2=true option

2026-03-27 13:59:07 -04:00