llvm dev - May 2016 - LNT General Failure

Renato, Kristof,



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.



Cheers,

Arnaud


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

Hi Renato,

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.

Thanks,

Kristof

On 29 May 2016, at 14:28, Renato Golin <renato.golin at
linaro.org<mailto:renato.golin at linaro.org>> wrote:

Folks,

Its seems that the latest master restart has introduced a failure in
*many* test-suite bots:

 File
"/home/buildslave/buildslave/clang-cmake-aarch64-full/test/lnt/lnt/server/ui/decorators.py",
line 6, in <module>
   frontend = flask.Module(__name__)
AttributeError: 'module' object has no attribute 'Module'

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

http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/2208

http://lab.llvm.org:8011/builders/clang-native-arm-lnt/builds/18012

http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4347

http://lab.llvm.org:8011/builders/clang-ppc64le-linux-lnt/builds/2042

Any one has any idea?

cheers,
--renato

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160530/ba5f323f/attachment.html>

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

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