Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Flock test failed. #5679

Open
zhoucheng361 opened this issue Feb 19, 2025 · 0 comments · May be fixed by #5694
Open

CI: Flock test failed. #5679

zhoucheng361 opened this issue Feb 19, 2025 · 0 comments · May be fixed by #5694
Labels
kind/bug Something isn't working

Comments

@zhoucheng361
Copy link
Contributor

zhoucheng361 commented Feb 19, 2025

What happened:
https://github.com/juicedata/juicefs/actions/runs/13404626272/job/37442216353


go test ./pkg/meta/... -rapid.meta=sqlite3://test.db -rapid.seed=21172 -rapid.checks=100000 -rapid.steps=200 -run "TestFSOps" -v -failfast -count=1 -timeout=30m -cover -coverpkg=./pkg/...,./cmd/... -args -test.gocoverdir="/home/runner/work/juicefs/juicefs/cover"
warning: no packages being tested depend on matches for pattern ./cmd/...
	github.com/juicedata/juicefs/pkg/meta/pb		coverage: 0.0% of statements
=== RUN   TestFSOps
    random_test.go:2159: [rapid] failed after 0 tests: expect [] but got []
        To reproduce, specify -run="TestFSOps" -rapid.failfile="testdata/rapid/TestFSOps/TestFSOps-2025021903[11](https://github.com/juicedata/juicefs/actions/runs/13404626272/job/37442217461#step:6:12)06-2750.fail" (or -rapid.seed=21172)
        Failed test output:
    random_test.go:[12](https://github.com/juicedata/juicefs/actions/runs/13404626272/job/37442217461#step:6:13)6: [rapid] draw sid: 0x0
    random_test.go:2159: [rapid] draw action: "Flock"
    random_test.go:163: [rapid] draw uid: 0x0
    random_test.go:164: [rapid] draw gid: 0x0
    random_test.go:176: [rapid] draw node: 0x1
    random_test.go:1928: [rapid] draw owner: 0x0
    random_test.go:1929: [rapid] draw typ: 0x0
    random_test.go:1971: expect [] but got []
--- FAIL: TestFSOps (3.81s)

go test ./pkg/meta/... -rapid.meta=redis://127.0.0.1:6379/1 -rapid.seed=7908 -rapid.checks=100000 -rapid.steps=200 -run "TestFSOps" -v -failfast -count=1 -timeout=30m -cover -coverpkg=./pkg/...,./cmd/... -args -test.gocoverdir="/home/runner/work/juicefs/juicefs/cover"
warning: no packages being tested depend on matches for pattern ./cmd/...
	github.com/juicedata/juicefs/pkg/meta/pb		coverage: 0.0% of statements
=== RUN   TestFSOps
    random_test.go:2159: [rapid] failed after 0 tests: expect [] but got []
        To reproduce, specify -run="TestFSOps" -rapid.failfile="testdata/rapid/TestFSOps/TestFSOps-2025021903[11](https://github.com/juicedata/juicefs/actions/runs/13404626272/job/37442216353#step:6:12)10-3927.fail" (or -rapid.seed=7908)
        Failed test output:
    random_test.go:[12](https://github.com/juicedata/juicefs/actions/runs/13404626272/job/37442216353#step:6:13)6: [rapid] draw sid: 0x0
    random_test.go:2159: [rapid] draw action: "Flock"
    random_test.go:163: [rapid] draw uid: 0x0
    random_test.go:164: [rapid] draw gid: 0x0
    random_test.go:176: [rapid] draw node: 0x1
    random_test.go:1928: [rapid] draw owner: 0x0
    random_test.go:1929: [rapid] draw typ: 0x0
    random_test.go:1971: expect [] but got []
--- FAIL: TestFSOps (1.05s)
FAIL
coverage: 4.3% of statements in ./pkg/..., ./cmd/...
FAIL	github.com/juicedata/juicefs/pkg/meta	1.410s

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?

Environment:

  • JuiceFS version (use juicefs --version) or Hadoop Java SDK version:
  • Cloud provider or hardware configuration running JuiceFS:
  • OS (e.g cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Object storage (cloud provider and region, or self maintained):
  • Metadata engine info (version, cloud provider managed or self maintained):
  • Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
  • Others:
@zhoucheng361 zhoucheng361 added the kind/bug Something isn't working label Feb 19, 2025
@jiefenghuang jiefenghuang linked a pull request Feb 25, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant