[Release-job-failures] Release of openstack-infra/shade failed
sean.mcginnis at gmail.com
Wed Oct 24 14:11:45 UTC 2018
On Wed, Oct 24, 2018 at 12:08 AM Tony Breeds <tony at bakeyournoodle.com>
> On Wed, Oct 24, 2018 at 03:23:53AM +0000, zuul at openstack.org wrote:
> > Build failed.
> > - release-openstack-python3
> : POST_FAILURE in 2m 18s
> So this failed because pypi thinks there was a name collision:
> HTTPError: 400 Client Error: File already exists. See
> https://pypi.org/help/#file-name-reuse for url:
> AFACIT the upload was successful:
> shade-1.27.2-py2-none-any.whl :
> shade-1.27.2-py2.py3-none-any.whl :
> shade-1.27.2.tar.gz :
> The strange thing is that the tar.gz was uploaded *befoer* the wheel
> even though our publish jobs explictly do it in the other order and the
> timestamp of the tar.gz doesn't match the error message.
> SO I think we have a bug somewhere, more digging tomorrow
> Yours Tony.
Looks like this was another case of conflicting jobs. This still has both
and release-openstack-python jobs running, so I think it ended up being a
race between the two of
which one got to pypi first.
I think the "fix" is to get the release-openstack-python out of there now
that we are able to run the
Python 3 version.
On the plus side, all of the subsequent jobs passed, so the package is
published, the announcement
went out, and the requirements update patch was generated.
> Release-job-failures mailing list
> Release-job-failures at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Release-job-failures