llvm dev - Jun 2017 - Test-suite bots red because of missing import

So, in the end looks like this setuptools 36 was deleted from pypi. There is an
issue [1] open on setuptools.

I can confirm by trying to force to install this version:

$ pip install setuptools==36.0.0
Collecting setuptools==36.0.0
  Could not find a version that satisfies the requirement setuptools==36.0.0
(from versions:<many version numbers>)
No matching distribution found for setuptools==36.0.0

I assume the builds will start to work again without any necessary change for
the moment.

We can still try to make a few changes on buildbot jobs to make the scripts less
reliant on the latest from pypi.
If you want to go ahead that way, let me know.

[1] https://github.com/pypa/setuptools/issues/1042


- Leandro


From: Diana Picus [mailto:diana.picus at linaro.org]
Sent: 01 June 2017 11:11
To: Leandro Nunes
Cc: Kristof Beyls; llvm-dev; nd
Subject: Re: [llvm-dev] Test-suite bots red because of missing import

Sounds great. Thanks for working on it, Leandro!

On 1 June 2017 at 12:08, Leandro Nunes <Leandro.Nunes at arm.com> wrote:
Hi,

There was a new Python setuptools release (36.0.0) today, that caused this
compatibility issue.
The suggestion to stop breaking the builds is to add a static setuptools version
on lnt's requirements.client.txt.

The latest known compatible version is 35.0.2. I have tested it building a LNT
sandbox and it seems to works.

setuptools==35.0.2

I'll create a bug on LNT so we can investigate in detail and push this
change on a code review in a few minutes.


thanks
Leandro

PS: sorry about the 'confidentiality footer'. Will be removed soon.


From: Kristof Beyls
Sent: 01 June 2017 10:59
To: Diana Picus; Leandro Nunes
Cc: llvm-dev; nd
Subject: Re: [llvm-dev] Test-suite bots red because of missing import

Adding Leandro - he saw this on some of our internal bots too.

On 1 Jun 2017, at 11:21, Diana Picus via llvm-dev <llvm-dev at
lists.llvm.org> wrote:

Hi all,

It seems some of the test-suite bots are red because they can't find the six
module anymore. See e.g.
http://lab.llvm.org:8011/builders/clang-cmake-aarch64-quick/builds/6867
http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/5727

Does anyone know how to fix this?

Thanks,
Diana
_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.

IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.

On 1 June 2017 at 12:18, Leandro Nunes via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> So, in the end looks like this setuptools 36 was deleted from pypi. There
is an issue [1] open on setuptools.
This happens every so often. We shouldn't be relying on specific
versions, but probably in ranges.

> We can still try to make a few changes on buildbot jobs to make the scripts
less reliant on the latest from pypi.
We moved to specific versions because this didn't work, as it would
break assumptions.

What we need to to have ">=" and "<=" instead of
"==" or latest.

Adding Chris who may know of the right fix for those cases.

cheers,
--renato

We have both back and forward incompatibilities, so == is best.

I tried updating a bunch of these a while back.  I was able to update a bunch no
problem.

For packages we depend on transitively, I think just listing the package with no
qualifier is fine. For our core packages (Flask, SQLAlchemy, Jinja, setuptools),
we’ll probably have to make an effort to keep up to date.
> On Jun 1, 2017, at 4:24 AM, Renato Golin <renato.golin at linaro.org>
wrote:
> 
> On 1 June 2017 at 12:18, Leandro Nunes via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> So, in the end looks like this setuptools 36 was deleted from pypi.
There is an issue [1] open on setuptools.
> 
> This happens every so often. We shouldn't be relying on specific
> versions, but probably in ranges.
> 
> 
>> We can still try to make a few changes on buildbot jobs to make the
scripts less reliant on the latest from pypi.
> 
> We moved to specific versions because this didn't work, as it would
> break assumptions.
> 
> What we need to to have ">=" and "<=" instead of
"==" or latest.
> 
> Adding Chris who may know of the right fix for those cases.
> 
> cheers,
> --renato