mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-10-24 06:50:40 +02:00
Chris LuandDevin
f7af816ab4
* 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>
77 lines
2.3 KiB
YAML
77 lines
2.3 KiB
YAML
name: "FUSE Volume Server Failover Tests"
|
|
|
|
on:
|
|
pull_request:
|
|
paths:
|
|
- 'weed/command/mount*.go'
|
|
- 'weed/mount/**'
|
|
- 'weed/filer/**'
|
|
- 'weed/wdclient/**'
|
|
- 'weed/operation/upload_content.go'
|
|
- 'test/fuse_failover/**'
|
|
- '.github/workflows/fuse-failover.yml'
|
|
- '.github/actions/fix-fusermount-setuid/**'
|
|
push:
|
|
branches: [master]
|
|
paths:
|
|
- 'weed/command/mount*.go'
|
|
- 'weed/mount/**'
|
|
- 'weed/filer/**'
|
|
- 'weed/wdclient/**'
|
|
- 'weed/operation/upload_content.go'
|
|
- 'test/fuse_failover/**'
|
|
- '.github/workflows/fuse-failover.yml'
|
|
- '.github/actions/fix-fusermount-setuid/**'
|
|
|
|
concurrency:
|
|
group: ${{ github.workflow }}-${{ github.event.pull_request.number || (github.event_name == 'push' && github.ref) || github.run_id }}
|
|
cancel-in-progress: ${{ github.event_name == 'pull_request' || (github.event_name == 'push' && !startsWith(github.ref, 'refs/tags/')) }}
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
fuse-failover:
|
|
name: FUSE Volume Server Failover
|
|
runs-on: ubuntu-22.04
|
|
timeout-minutes: 40
|
|
|
|
steps:
|
|
- name: Check out code
|
|
uses: actions/checkout@v7
|
|
with:
|
|
persist-credentials: false
|
|
|
|
- name: Set up Go
|
|
uses: actions/setup-go@v7
|
|
with:
|
|
go-version-file: 'go.mod'
|
|
|
|
- name: Configure FUSE
|
|
run: |
|
|
# Nothing to install: fuse3 ships fusermount3 and is pre-installed,
|
|
# and go-fuse is pure Go, so the libfuse headers were never linked
|
|
# against.
|
|
echo 'user_allow_other' | sudo tee -a /etc/fuse.conf
|
|
sudo chmod 644 /etc/fuse.conf
|
|
|
|
- name: Repair the fusermount3 setuid bit
|
|
uses: ./.github/actions/fix-fusermount-setuid
|
|
|
|
- name: Build SeaweedFS
|
|
run: go build -o weed/weed -buildvcs=false ./weed
|
|
|
|
- name: Run failover integration tests
|
|
timeout-minutes: 35
|
|
env:
|
|
WEED_BINARY: ${{ github.workspace }}/weed/weed
|
|
run: go test -v -count=1 -timeout=30m ./test/fuse_failover/...
|
|
|
|
- name: Upload logs on failure
|
|
if: failure()
|
|
uses: actions/upload-artifact@v7
|
|
with:
|
|
name: fuse-failover-test-logs
|
|
path: /tmp/seaweedfs-fuse-failover-logs/
|
|
retention-days: 3
|