From 84e44f2607006a6b7619bf864ef17453fced571d Mon Sep 17 00:00:00 2001 From: Weixie Cui Date: Tue, 9 Jun 2026 20:00:00 +0800 Subject: [PATCH] cmd/devp2p/internal/v5test: fix challenge data mismatch error Label the actual and expected challenge data values in the WHOAREYOU resend test failure. This makes the diagnostic clear when the resent ChallengeData does not match the original challenge. --- cmd/devp2p/internal/v5test/discv5tests.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/devp2p/internal/v5test/discv5tests.go b/cmd/devp2p/internal/v5test/discv5tests.go index 4dc2507693..17d39d5ad0 100644 --- a/cmd/devp2p/internal/v5test/discv5tests.go +++ b/cmd/devp2p/internal/v5test/discv5tests.go @@ -186,7 +186,7 @@ func (s *Suite) TestHandshakeResend(t *utesting.T) { t.Fatalf("wrong nonce %x in WHOAREYOU (want %x)", resp.Nonce[:], challenge1.Nonce[:]) } if !bytes.Equal(resp.ChallengeData, challenge1.ChallengeData) { - t.Fatalf("wrong ChallengeData in resent WHOAREYOU (want %x)", resp.ChallengeData, challenge1.ChallengeData) + t.Fatalf("wrong ChallengeData in resent WHOAREYOU: got %x, want %x", resp.ChallengeData, challenge1.ChallengeData) } resp.Node = conn.remote default: