Bug report criteria

• This bug report is not security related, security issues should be disclosed privately via security@etcd.io.
• 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?

After the Go 1.22 update, the coverage workflow has been failing. See https://github.com/etcd-io/etcd/actions/workflows/coverage.yaml.

After some investigation, it is possible to duplicate the issue locally. It seems like v1.22 had a significant coverage rewrite, which appears to be broken.

What did you expect to happen?

The coverage workflow should run as expected.

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

Currently, the main branch is presenting the issue. Refer to https://github.com/etcd-io/etcd/actions/workflows/coverage.yaml to see the failed runs.

Anything else we need to know?

No response

Etcd version (please run commands below)

$ etcd --version
# paste output here

$ etcdctl version
# paste output here

Etcd configuration (command line flags or environment variables)

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