Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2576

TlsSocketTest.TestRecvFailure is flaky

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.0
    • Fix Version/s: 1.10.0
    • Component/s: security
    • Labels:
      None

      Description

      This test seems destined to be flaky in TSAN environments.

      The initial sleep is there so that the stop signal to EchoServer is sent while it's blocked inside the echo loop. That appears to be how we can safely assert that one write and one recv both succeed, while the second recv fails.

      However, it's possible for EchoServer to be so slow to start that 100 ms isn't enough, and the stop signal reaches it before it enters the loop. Then the first write will fail like this:

      /home/jenkins-slave/workspace/kudu-master/3/src/kudu/security/tls_socket-test.cc:230
      Failed
      Bad status: Network error: BlockingWrite error: failed to write to TLS socket: Connection reset by peer
      

      Alexey said he'd take a look at this.

        Attachments

          Activity

            People

            • Assignee:
              wdberkeley William Berkeley
              Reporter:
              adar Adar Dembo
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: