Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

circuitv2: flaky TestReservationFailures/unsupported_protocol #1730

Closed
marten-seemann opened this issue Sep 2, 2022 · 0 comments · Fixed by #1899 or #1898
Closed

circuitv2: flaky TestReservationFailures/unsupported_protocol #1730

marten-seemann opened this issue Sep 2, 2022 · 0 comments · Fixed by #1899 or #1898
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@marten-seemann
Copy link
Contributor

  === RUN   TestReservationFailures/unsupported_protocol
      reservation_test.go:100: 
          	Error Trace:	D:\a\go-libp2p\go-libp2p\p2p\protocol\circuitv2\client\reservation_test.go:100
          	Error:      	"Application error 0x0: peer:12D3KooWDuwgsbf9CcVe1euAXgjn8CxtHKjQdhuLGiJ7Na4NWinE: cannot reserve inbound connection: resource limit exceeded" does not contain "protocol not supported"
          	Test:       	TestReservationFailures/unsupported_protocol
  === RUN   TestReservationFailures/wrong_message_type
  === RUN   TestReservationFailures/unknown_status
  === RUN   TestReservationFailures/invalid_time
  === RUN   TestReservationFailures/invalid_voucher
  --- FAIL: TestReservationFailures (0.64s)
      --- FAIL: TestReservationFailures/unsupported_protocol (0.20s)
      --- PASS: TestReservationFailures/wrong_message_type (0.09s)
      --- PASS: TestReservationFailures/unknown_status (0.08s)
      --- PASS: TestReservationFailures/invalid_time (0.17s)
      --- PASS: TestReservationFailures/invalid_voucher (0.10s)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
1 participant