LNT Python problem?

http://lab.llvm.org:8011/builders/clang-cmake-aarch64-quick/builds/8218

Searching for aniso8601>=0.82
Reading Links for aniso8601
Download error on https://pypi.python.org/simple/aniso8601/: [Errno
107] Transport endpoint is not connected -- Some packages may not be
found!
Couldn't find index page for 'aniso8601' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading Simple index
No local packages or download links found for aniso8601>=0.82
error: Could not find suitable distribution for
Requirement.parse('aniso8601>=0.82')

No changes since last successful build on any bot on our side, maybe a
Python issue like the last time?

Is there a way to cache those packages locally?

cheers,
--renato

Lets deal with this in a PR:

https://llvm.org/bugs/show_bug.cgi?id=28347

I’m surprised how often this is happening. I propose we lock all the dependency versions in LNT, and upgrade them on some cycle (maybe yearly). Otherwise this will happen every time we have a dependent package’s default version change. We have always done this in the reqirements.txt file, and that has worked really well in our server deployments.

I’m surprised how often this is happening. I propose we lock all the dependency versions in LNT, and upgrade them on some cycle (maybe yearly). Otherwise this will happen every time we have a dependent package’s default version change. We have always done this in the reqirements.txt file, and that has worked really well in our server deployments.

So, I thought about this being the same as last time, but here it's

=, so unless they removed all versions newer than 0.82, this

requirement should work!

Requirement.parse('aniso8601>=0.82')

And funny enough, it worked on the next build... So, I don't really
think this is the same thing as before...

Could it be network problems? (and odd way to manifest, but...) That's
why I didn't create a bug, because it may very well be on my side.

cheers,
--renato