Comment 2 for bug 1449136

Been digging into this and these readtimeouts are now retried by pip which means they aren't often the source of a job failure. Instead you hit this once or twice in a job but the GETs get retried and everything moves on happily.

I've been trying to find a better query for logstash that will show us when this actually is a failure and I think you get something like this when the package (tox in this case) can't be installed at all:

  Could not find a version that satisfies the requirement tox (from versions: )
No matching distribution found for tox

So I will be working to update the query for this bug to track ^.