Failing QuicUdpSocketTest.ReadReceiveTimestamp tests on Chromium Linux builds

[Shubham Aggarwal]

Hi,

The following test and its variants are failing on our Linux builds for Microsoft Edge. They also fail similarly on my local machine when building Chromium (I am running Ubuntu 18.04.5 LTS). 

-NonIos/QuicUdpSocketTest.ReadReceiveTimestamp/0

-PlatformIndependent/QuicUdpSocketTest.ReadReceiveTimestamp/0

-PlatformIndependent/QuicUdpSocketTest.ReadReceiveTimestamp/1

-PlatformIndependent/QuicUdpSocketTest.ReadReceiveTimestamp/2

The failure is interesting because only the first test to run out of the four fails and the rest pass. They all fail if ran individually. 

I have also previously seen a different failure pattern where one of the tests was only flaky (passing 20% of the time) but now they all fail absolutely.

The code tests fairly low level functionality and I haven't been able to root cause the issue. 

I wanted to ask if this is a known issue and if not, can I get some help resolving this. 

Thanks,

Shubham

[chepe caudillo]

[Ian Swett]

Thanks for the heads up, can you file a crbug under QUIC and we can follow up there?

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/58bbeaac-94b8-49d0-a235-1c32c7d7ec8an%40chromium.org.

[Shubham Aggarwal]

Thanks for your response. Here's the link to the CRBug: crbug.com/1168506

Shubham