-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Enable QUIC client by default. Add arg to disable QUIC client. #26879
Enable QUIC client by default. Add arg to disable QUIC client. #26879
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
Looks like The test creates a list of IPAddresses (and ports), creates connections using the addresses, and then looks up the table using address as the key. With QUIC, we are adding an offset (6) to the port. So the key (address/port) in the table is different than what the test had created.
Maybe the test can be disabled as part of this PR, and an issue can be created to fix the test as a follow up PR? |
@willhickey Seems like this commit is causing these two tests to timeout in coverage CI:
The CI was also failing: |
I briefly looked at these two tests. The receiver for the forwarded transactions is UDP based (in the tests). Since now we are using QUIC for forwarding the transaction, nothing is received on the UDP port, and it waits for ever.
The solution will be start a QUIC streamer on the receiver port, and use the channel provided to the streamer to receive the packets. |
@willhickey I see that in #26912 you are commenting out the tests. There is no tracking issues to fix those tests and you commenting them out prevents compile time checks that code still compiles.
|
This commit also broke:
|
Yeah... there are a bunch of broken tests. PR #26913 has landed to revert this so CI should be unblocked. I'll work on cleaning up the tests and open a new PR |
solana-labs#26913) Revert "Enable QUIC client by default. Add arg to disable QUIC client. (solana-labs#26879)" This reverts commit 4c29750.
Problem
--tpu-use-quic
, but doesn't by defaultSummary of Changes