Curious on why QUIC works on 3.2 but not 3.3 in PUT on NonStop #24431
Replies: 4 comments 6 replies
-
The code for test 11 reads as follows:
If I understand things right the test idea is as follows: create 5 server threads (
I suspect the error must be coming from child 0
I need to check history of this test and related area to better understand why it is seen on 3.3 on not in 3.2. |
Beta Was this translation helpful? Give feedback.
-
Fantastic! That did it. I'm going to put this into a fix for 3.3 and 3.4 - also should go to 3.2, which I think is only coincidentally working. |
Beta Was this translation helpful? Give feedback.
-
Converted to an issue and pull request. Thanks @nhorman and @Sashan. |
Beta Was this translation helpful? Give feedback.
-
thanks for the quick turnaround here. I agree with the analysis by @nhorman. The test seems to appear in 3.3 for the first time when support for multistream clients has been introduced. Putting all bits together this is what happens:
However when we execute line 2023 the stream is gone already. |
Beta Was this translation helpful? Give feedback.
-
Is there some fundamental difference in how QUIC is implemented between 3.2 and 3.3? I have
70-test_quic_lcidm.t
failing pretty broadly on timeouts. I'm not willing to say this a bug at this point but would raise one if it turns out to be.Basically the test runs and then fails starting here (in 3.3 across pretty much all commits):
Beta Was this translation helpful? Give feedback.
All reactions