[tor-bugs] #33598 [Core Tor/Chutney]: chutney does not fail on some SOCKS errors

[Tor Bug Tracker & Wiki]

#33598: chutney does not fail on some SOCKS errors
-------------------------------------------------+-------------------------
 Reporter:  teor                                 |          Owner:  c
     Type:  defect                               |         Status:
                                                 |  assigned
 Priority:  Medium                               |      Milestone:
Component:  Core Tor/Chutney                     |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  ipv6, prop311, outreachy-ipv6, easy  |  Actual Points:
Parent ID:  #33050                               |         Points:  1
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor55-can
-------------------------------------------------+-------------------------
Changes (by c):

 * owner:  (none) => c
 * status:  new => assigned
 * cc: c@… (added)


Comment:

 Assuming workaround is at
 [https://gitweb.torproject.org/chutney.git/tree/lib/chutney/Traffic.py#n441
 Traffic.py:441]? I see the timeout was adjusted in
 [https://gitweb.torproject.org/chutney.git/commit/?id=95ce144c 95ce144c]
 which has more changes than just that line.

 What's a reproducible way to cause a failure case here? Or, at least, will
 decreasing the timeout back to `0.2` be enough to encourage failure?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33598#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online