Operations are sporadically timing out when they go through the SOCKS 5 proxy.
agent:2019/06/12 02:11:54 build.go:197: QWARN : tst_QFtp::rename(WithSocks5Proxy:relPath01) tst_QFtp::fileExists: Network operation timed out
agent:2019/06/12 02:11:54 build.go:197: FAIL! : tst_QFtp::rename(WithSocks5Proxy:relPath01) 'fileExists( host, 21, user, password, newfile, cdDir )' returned FALSE. ()
agent:2019/06/12 02:11:54 build.go:197: Loc: [tst_qftp.cpp(1179)]
As a result this test has been quite flaky in the last 30 days, see the grafana dashboard. Full coin log here.
UPDATE: Thanks to Ryan Chu's comment on
QTQAINFRA-2275, we know that the timeouts are not related to the external qt-test-server, since the test is using docker containers.
UPDATE2: The timeout is easily reproducible on a CPU loaded VM, running the rename test with data WithSocks5Proxy, utilising two docker containers: one with danted and one with vsftpd. It is not reproducible with data WithoutProxy no matter how loaded the VM is. It is not reproducible without docker containers, no matter how loaded the server and the client machines are.