Since introduction of compaction in https://github.com/etcd-io/etcd/pull/17833 we started getting traffic.go:129: Requiring minimal 100.000000 qps before failpoint injection for test results to be reliable, got 89.482132 qps
I would like to propose to create a separate Compaction and LazyFS as they might be too heavy to CI. For example separate TestRobustnessExploratory/Etcd/LowTraffic/ClusterOfSize1 into:
Which Github Action / Prow Jobs are flaking?
https://testgrid.k8s.io/sig-etcd-robustness#ci-etcd-robustness-amd64
Which tests are flaking?
TestRobustnessExploratory/Kubernetes/LowTraffic/ClusterOfSize1/LazyFS TestRobustnessExploratory/Etcd/LowTraffic/ClusterOfSize1/LazyFS
Github Action / Prow Job link
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-etcd-robustness-amd64/1799048278302527488
Reason for failure (if possible)
Since introduction of compaction in https://github.com/etcd-io/etcd/pull/17833 we started getting
traffic.go:129: Requiring minimal 100.000000 qps before failpoint injection for test results to be reliable, got 89.482132 qps
I would like to propose to create a separate Compaction and LazyFS as they might be too heavy to CI. For example separate TestRobustnessExploratory/Etcd/LowTraffic/ClusterOfSize1 into:
TODO:
Anything else we need to know?
No response