Robustness test failure: Progress notify does not match

[siyuanfoundation]

Bug report criteria

• This bug report is not security related, security issues should be disclosed privately via etcd maintainers.
• This is not a support request or question, support requests or questions should be raised in the etcd discussion forums.
• You have read the etcd bug reporting guidelines.
• Existing open issues along with etcd frequently asked questions have been checked and this is not a duplicate.

What happened?

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-etcd-robustness-main-amd64/1868726984805191680

This seems to be recurring failure.

What did you expect to happen?

succeed.

How can we reproduce it (as minimally and precisely as possible)?

n.a.

Anything else we need to know?

No response

Etcd version (please run commands below)

v3.6

Etcd configuration (command line flags or environment variables)

{Failed === RUN TestRobustnessExploratory/EtcdTrafficDeleteLeases/ClusterOfSize1/beforeWritebackBuf=panic
watch.go:140: Progress notify does not match, expect: true, got: false
--- FAIL: TestRobustnessExploratory/EtcdTrafficDeleteLeases/ClusterOfSize1/beforeWritebackBuf=panic (4.09s)
}

Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)

$ etcdctl member list -w table
# paste output here

$ etcdctl --endpoints=<member list> endpoint status -w table
# paste output here

Relevant log output

No response

[siyuanfoundation]

/cc @fuweid