Uploaded image for project: 'Smack'
  1. Smack
  2. SMACK-807

Socks5ByteStreamManagerTest sometimes fails

    Details

    • Type: Bug
    • Status: Open (View workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects versions: 4.2.3
    • Fix versions: None
    • Components: Extensions
    • Labels:
    • Expected Effort:
      Unknown

      Description

      Sometimes the JUnit test suite of the Socks5ByteStream code fails. This might be a race condition, but I'm not sure.

      :smack-extensions:test
org.jivesoftware.smackx.bytestreams.socks5.Socks5ByteStreamManagerTest > shouldUseMultipleAddressesForLocalSocks5Proxy FAILED
    org.jivesoftware.smack.SmackException at Socks5ByteStreamManagerTest.java:831
org.jivesoftware.smackx.bytestreams.socks5.Socks5ByteStreamManagerTest > shouldPrioritizeSecondSocks5ProxyOnSecondAttempt FAILED
    java.lang.IllegalStateException at Socks5ByteStreamManagerTest.java:894
org.jivesoftware.smackx.bytestreams.socks5.Socks5ByteStreamManagerTest > shouldNegotiateSocks5BytestreamAndTransferData FAILED
    java.lang.IllegalStateException at Socks5ByteStreamManagerTest.java:739
247 tests completed, 3 failed
:smack-extensions:test FAILED

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              vanitasvitae
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: