libp2p / libp2p/go-libp2p

quic: flaky TestResourceManagerSuccess

Open
#1,741 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
Go
Stars
6.9k
Forks
1.3k
Avg merge
13d 21h
Merged PRs (30d)
1

Description

```
=== RUN TestResourceManagerSuccess
=== RUN TestResourceManagerSuccess/reuseport_on
conn_test.go:56: using a Ed25519 key: 12D3KooWQNMRwvcYc5LczS6ivsrChLgUzn7jLYCgfAzxS5fBUhKd
conn_test.go:56: using a Secp256k1 key: 16Uiu2HAm1EqLsLBYkVEKCKFYy52eaLT5PaStbQsnQ58duYv9GABo
conn_test.go:162: received conn
=== RUN TestResourceManagerSuccess/reuseport_off
conn_test.go:56: using a Secp256k1 key: 16Uiu2HAmTLkUVtnkdb5ikvXVhEiwneT8iDmDA7gyb5YGauNEoHLd
conn_test.go:56: using a ECDSA key: Qmf3nPknM7GfmmMJCkGin6neHkvjd6XExMkrnjYyDsQ6LH
conn_test.go:138:
Error Trace: /home/runner/work/go-libp2p/go-libp2p/p2p/transport/quic/conn_test.go:138
/home/runner/work/go-libp2p/go-libp2p/p2p/transport/quic/conn_test.go:121
Error: Received unexpected error:
cannot use different stateless reset keys on the same packet conn
Test: TestResourceManagerSuccess/reuseport_off
--- FAIL: TestResourceManagerSuccess (0.03s)
--- PASS: TestResourceManagerSuccess/reuseport_on (0.02s)
--- FAIL: TestResourceManagerSuccess/reuseport_off (0.01s)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running TestResourceManagerSuccess and inspect p2p/transport/quic/conn_test.go, especially lines 56, 121, 138, and 162. Trace why the reuseport_off case reports different stateless reset keys, then make both subtests pass reliably without the unexpected error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.