[llvm-dev] LNT General Failure

Arnaud De Grandmaison via llvm-dev llvm-dev at lists.llvm.org
Mon May 30 12:01:26 PDT 2016

I honestly do not know how to fix that --- I would otherwise I've committed a fix.

I've been able to hack it locally exploiting the very same lit limitation then the one we're stumbling on (i.e it does not resolve dependency correctly and only pick-up the first constraint).
You need to make sure the Flask constraint is seen first, even before using the requirements.txt so on the command line before loading the requirements.txt.

> -----Original Message-----
> From: Renato Golin [mailto:renato.golin at linaro.org]
> Sent: 30 May 2016 20:42
> To: Arnaud De Grandmaison
> Cc: Kristof Beyls; nd; llvm-dev at lists.llvm.org
> Subject: Re: LNT General Failure
> On 30 May 2016 at 12:25, Arnaud De Grandmaison
> <Arnaud.DeGrandmaison at arm.com> wrote:
> > I confirm this is due to the latest Flask --- Flask-0.11 was released
> > this weekend --- and for some unknown (to me at least) reason,
> > although LNT's requirements.txt pins Flask to version 0.10.1, pip installs
> Flask-0.11.
> > Forcing Flask to 0.10.1 gets the situation back to normal.
> Do you know where to change that in LNT? If you could commit a fix, it'd
> probably get all our bots fixed, too.
> thanks!
> --renato

More information about the llvm-dev mailing list