You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| // Get all Pods in advance to check if ippool and endpoint are deleted
github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x4baf89?, 0xc000036fa8?})
/home/runner/work/spiderpool/spiderpool/vendor/github.com/onsi/ginkgo/v2/internal/node.go:472
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
/home/runner/work/spiderpool/spiderpool/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:894
github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 22
/home/runner/work/spiderpool/spiderpool/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:881
[FAILED] failed to check pod status in namespace gc-chaos-ns-2314-849861788, error <nil>
Unexpected error:
<*errors.errorString | 0xc0002e4000>:
time out to wait podList ready
{
s: "time out to wait podList ready",
}
occurred
In [It] at: /home/runner/work/spiderpool/spiderpool/test/e2e/reclaim/chaos_test.go:382 @ 12/29/24 20:38:15.293
< Exit [It] Multiple resource types compete for a single IPPool. In scenarios of creation, scaling up/down, and deletion, GC all can correctly handle IP addresses. - /home/runner/work/spiderpool/spiderpool/test/e2e/reclaim/chaos_test.go:269 @ 12/29/24 20:38:15.293 (9m13.387s)
> Enter [DeferCleanup (Each)] Chaos Testing of GC - /home/runner/work/spiderpool/spiderpool/test/e2e/reclaim/chaos_test.go:242 @ 12/29/24 20:38:15.293
If the use case fails, the cleanup step will be skipped
< Exit [DeferCleanup (Each)] Chaos Testing of GC -
action url: https://github.com/spidernet-io/spiderpool/actions/runs/12538326687
The text was updated successfully, but these errors were encountered: