On 2018-10-24 16:08:26 +1100 (+1100), Tony Breeds wrote:
> On Wed, Oct 24, 2018 at 03:23:53AM +0000, z...@openstack.org wrote:
> > Build failed.
> > 
> > - release-openstack-python3 
> > http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/
> >  : POST_FAILURE in 2m 18s
> 
> So this failed because pypi thinks there was a name collision[1]:
>  HTTPError: 400 Client Error: File already exists. See 
> https://pypi.org/help/#file-name-reuse for url: 
> https://upload.pypi.org/legacy/
> 
> AFACIT the upload was successful:
> 
> shade-1.27.2-py2-none-any.whl                          : 2018-10-24T03:20:00 
> d30a230461ba276c8bc561a27e61dcfd6769ca00bb4c652a841f7148a0d74a5a
> shade-1.27.2-py2.py3-none-any.whl                      : 2018-10-24T03:20:11 
> 8942b56d7d02740fb9c799a57f0c4ff13d300680c89e6f04dadb5eaa854e1792
> shade-1.27.2.tar.gz                                    : 2018-10-24T03:20:04 
> ebf40040b892f3e9bd4229fd05fff7ea24a08c51e46b7f2d8b3901ce34f51cbf
[...]

I think PyPI is right. Note the fact that there are not two but
*three* artifacts there. We shouldn't be building both a py2 and
py2.py3 wheel. The log you linked is uploaded
shade-1.27.2-py2.py3-none-any.whl and tried (but failed) to upload
shade-1.27.2.tar.gz. So where did shade-1.27.2-py2-none-any.whl come
from then? Hold onto your hats folks:

http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python/f38f2b9/job-output.txt.gz#_2018-10-24_03_20_02_134223

I suppose we don't expect a project to run both the
release-openstack-python and release-openstack-python3 jobs on the
same tags.
-- 
Jeremy Stanley

Attachment: signature.asc
Description: PGP signature

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to