iirc fron a previous investigation, here are some details on the issue: The two failing tests are always * connect_many_timeout * connect_timeout
If I'm correct, those tests are trying to reach 10.255.255.1, which is supposed to be unavailable and raise a timeout but, maybe due to the proxy (maybe not, I'm not sure), that address is reachable in the infra, making the connection not to timeout, except when something (machine, network, etc...) is slow enough, and that explains why we sometimes see them pass. One easy way to reproduce the problem locally is to have the 10.255.255.1 IP reachable. In the `rust-reqwest` source package: ``` sudo ip addr add 10.255.255.1/32 dev enp5s0 sudo ip addr add 10.255.255.2/32 dev enp5s0 # only for connect_many_timeout, that also uses it cargo test timeout ``` Maybe one possible way forward could be to blackhole those IPs on the testbed with our setup scripts. I'll try to experiment a bit with that solution and see how it goes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080346 Title: autopkg test timeouts on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-reqwest/+bug/2080346/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
