[llvm-dev] LNT General Failure
Arnaud De Grandmaison via llvm-dev
llvm-dev at lists.llvm.org
Mon May 30 04:25:25 PDT 2016
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.
Reading pip's documentation makes me think it's not able to resolve dependencies correctly in our case.
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Kristof Beyls via llvm-dev
Sent: 30 May 2016 13:17
To: Renato Golin
Cc: LLVM Dev; nd
Subject: Re: [llvm-dev] LNT General Failure
We're also seeing this on internal bots.
My first guess is that it was triggered by the Flask package getting updated at Pypi on 29th of May, see https://pypi.python.org/pypi/Flask.
I haven't investigated further at this point.
On 29 May 2016, at 14:28, Renato Golin <renato.golin at linaro.org<mailto:renato.golin at linaro.org>> wrote:
Its seems that the latest master restart has introduced a failure in
*many* test-suite bots:
line 6, in <module>
frontend = flask.Module(__name__)
AttributeError: 'module' object has no attribute 'Module'
Any one has any idea?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev