* ci: cancel superseded workflow runs on PR pushes
PR-triggered workflows without a concurrency group keep running (and
holding runner slots) after a force-push or quick follow-up commit
supersedes them. Add the same group/cancel-in-progress block the go
workflow already uses, keyed on head_ref, to the remaining PR workflows.
Generated with [Devin](https://devin.ai)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* ci: key concurrency groups on PR number or ref, not head_ref
github.head_ref is empty on tag pushes and manual runs (every run then
shares one group and cancels the last) and collides across forks when
two PRs share a branch name. pull_request.number is unique per PR;
github.ref covers push/tag/dispatch. Applied to all workflows using the
pattern, including pre-existing ones.
Generated with [Devin](https://devin.ai)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* ci: restrict cancel-in-progress to PR and branch-push runs
* ci: serialize container_latest manual runs by destination tag
Two workflow_dispatch runs sharing an image_tag could otherwise build
concurrently: their per-arch images publish to the same platform tags,
so one run's create-manifest job can combine platforms from different
source refs. Group dispatch runs by the destination tag (with
cancel-in-progress already disabled for non-PR/non-branch events) so
same-tag publishes queue instead of interleaving.
* ci: serialize manual publish runs by destination tag in remaining container workflows
* ci: group foundationdb release dispatch runs by release tag
A manual run now shares the tag-push concurrency group for the same
release, so a re-publish of a tag queues behind (or ahead of) the push
run instead of racing it on the same image tag.
Generated with [Devin](https://devin.ai)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* ci: serialize foundationdb_version dispatch runs by destination tag
Two manual runs resolving to the same docker tag now share a concurrency
group (explicit image_tag, else the computed
foundationdb_<fdb>_seaweedfs_<ref> default), so they queue instead of
racing pushes to the same tag.
Generated with [Devin](https://devin.ai)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* ci: drop unsupported toLower() from foundationdb_version concurrency group
* ci: key rocksdb_version dispatch group on its published tag
* ci: queue publish runs via turnstyle instead of cancel-free shared groups
* Revert "ci: queue publish runs via turnstyle instead of cancel-free shared groups"
This reverts commit 039148f8d5.
* ci: queue same-tag publish runs instead of replacing the pending one
Dispatch/tag-only workflows can never cancel in progress, so opt their
concurrency groups into queue: max — up to 100 same-tag publishes wait
in line rather than each new dispatch cancelling the pending one.
---------
Co-authored-by: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
* ci: bring previously-uncovered integration tests into CI (#9281 follow-up)
Six integration test packages had _test.go files but no GitHub workflow
running them. The s3-sse-tests CI gap that let #8908's UploadPartCopy bug
(and the four cross-SSE copy bugs in #9281) ship undetected was an
instance of this same pattern. This change wires three of them into CI
and removes a fourth that was deadcode:
test/multi_master/ NEW workflow: multi-master-tests.yml
- 3-node master raft cluster failover/recovery (5 tests, ~65s)
test/testutil/ (run alongside multi_master)
- port-allocator regression test
test/s3/etag/ NEW workflow: s3-etag-acl-tests.yml
- PutObject ETag format regression for #7768 (must be pure MD5 hex,
not "<md5>-N" composite, for AWS Java SDK v2 compatibility)
test/s3/acl/ (same workflow as etag)
- object-ACL behavior on versioned buckets
test/s3/catalog_trino/ DELETED (deadcode)
- Single-file copy of test/s3tables/catalog_trino/trino_catalog_test.go
from a 2024 commit that was never iterated, while the
test/s3tables/ counterpart has been actively maintained (and IS
in CI via s3-tables-tests.yml's trino-iceberg-catalog-tests job).
Both workflows trigger only on changes to relevant code paths and use the
existing simple "build weed → run go test" pattern (no per-test-dir
Makefile boilerplate). The S3 workflow starts a single `weed mini`
shared by etag and acl, which keeps the job under 2 minutes on a fresh
runner.
Two tests remain knowingly uncovered:
test/s3/basic/ — order-dependent state across tests (TestListObjectV2
expects a bucket created by an earlier test, etc.) and uses the
deprecated aws-sdk-go v1. Treated as sample programs, not a
regression suite. Fixing them is out of scope for this PR.
test/s3/catalog_trino/ — see "DELETED" above.
Verified locally:
- go test -v -timeout=8m ./test/multi_master/... ./test/testutil/...
PASS (5 multi_master + 1 testutil tests, 64s)
- weed mini + go test ./test/s3/etag/... + go test ./test/s3/acl/...
PASS (8 etag + 5 acl tests, ~6s after server startup)
* ci: fix log-collector glob for multi-master tests (review feedback on #9283)
test/multi_master/cluster.go creates per-test temp dirs via
os.MkdirTemp("", "seaweedfs_multi_master_it_"), so the glob has to
match that prefix. The previous version looked for MasterCluster* /
TestLeader* / TestTwoMasters* / TestAllMasters* which never matches —
the failure-artifact upload would have been empty on a real failure.
Switch the find to /tmp/seaweedfs_multi_master_it_* (maxdepth 1) so it
actually picks up the per-node master*.log files under
<baseDir>/logs/.
Found by coderabbitai review on PR #9283.
