I think I've figured out why torsocks-ci-linux is failing on Jenkins!
So, the tests seem to assume that there is a tor process running that can receive their queries, and that it's on the internet, and that while on the internet it can connect to the Tor network.
Not crazy I guess!
But FWICT the Jenkins builder hasn't launched a Tor process, or has shut off access to the network. I guess that's why it's failing in test_dns.c
So, the question: Q1. Does torsocks really require for its tests that there exist a Tor process on port 9050 with access to the internet?
If the answer to Q1 is no, there is a bug in torsocks.
If the answer to Q1 is yes, there are three possible solutions I see: S1. Change torsocks so that no tests require a running Tor with access to the internet. S2. Change the Jenkins configuration so that it launches a tor client process for the torsocks test to use. S3. Divide the torsocks tests into the ones that need a Tor connected to the network, and the ones that do not. Only run the ones that do not when we're running under Jenkins.