[llvm-dev] LNT Python problem?
Chris Matthews via llvm-dev
llvm-dev at lists.llvm.org
Tue Jun 28 11:34:48 PDT 2016
Lets deal with this in a PR:
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.
> On Jun 28, 2016, at 1:50 AM, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> Searching for aniso8601>=0.82
> Reading https://pypi.python.org/simple/aniso8601/
> Download error on https://pypi.python.org/simple/aniso8601/: [Errno
> 107] Transport endpoint is not connected -- Some packages may not be
> Couldn't find index page for 'aniso8601' (maybe misspelled?)
> Scanning index of all packages (this may take a while)
> Reading https://pypi.python.org/simple/
> No local packages or download links found for aniso8601>=0.82
> error: Could not find suitable distribution for
> 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?
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
More information about the llvm-dev