<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Wed, Oct 24, 2018 at 12:08 AM Tony Breeds <<a href="mailto:tony@bakeyournoodle.com">tony@bakeyournoodle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Oct 24, 2018 at 03:23:53AM +0000, <a href="mailto:zuul@openstack.org" target="_blank">zuul@openstack.org</a> wrote:<br>
> Build failed.<br>
> <br>
> - release-openstack-python3 <a href="http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/" rel="noreferrer" target="_blank">http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/</a> : POST_FAILURE in 2m 18s<br>
<br>
So this failed because pypi thinks there was a name collision[1]:<br>
HTTPError: 400 Client Error: File already exists. See <a href="https://pypi.org/help/#file-name-reuse" rel="noreferrer" target="_blank">https://pypi.org/help/#file-name-reuse</a> for url: <a href="https://upload.pypi.org/legacy/" rel="noreferrer" target="_blank">https://upload.pypi.org/legacy/</a><br>
<br>
AFACIT the upload was successful:<br>
<br>
shade-1.27.2-py2-none-any.whl : 2018-10-24T03:20:00 d30a230461ba276c8bc561a27e61dcfd6769ca00bb4c652a841f7148a0d74a5a<br>
shade-1.27.2-py2.py3-none-any.whl : 2018-10-24T03:20:11 8942b56d7d02740fb9c799a57f0c4ff13d300680c89e6f04dadb5eaa854e1792<br>
shade-1.27.2.tar.gz : 2018-10-24T03:20:04 ebf40040b892f3e9bd4229fd05fff7ea24a08c51e46b7f2d8b3901ce34f51cbf<br>
<br>
The strange thing is that the tar.gz was uploaded *befoer* the wheel<br>
even though our publish jobs explictly do it in the other order and the<br>
timestamp of the tar.gz doesn't match the error message.<br>
<br>
SO I think we have a bug somewhere, more digging tomorrow<br>
<br>
Yours Tony.<br></blockquote><div><br></div><div>Looks like this was another case of conflicting jobs. This still has both release-openstack-python3</div><div>and release-openstack-python jobs running, so I think it ended up being a race between the two of</div><div>which one got to pypi first.</div><div><br></div><div>I think the "fix" is to get the release-openstack-python out of there now that we are able to run the</div><div>Python 3 version.</div><div><br></div><div>On the plus side, all of the subsequent jobs passed, so the package is published, the announcement</div><div>went out, and the requirements update patch was generated.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
[1] <a href="http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/job-output.txt.gz#_2018-10-24_03_20_15_264676" rel="noreferrer" target="_blank">http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/job-output.txt.gz#_2018-10-24_03_20_15_264676</a><br>
_______________________________________________<br>
Release-job-failures mailing list<br>
<a href="mailto:Release-job-failures@lists.openstack.org" target="_blank">Release-job-failures@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures</a><br>
</blockquote></div></div>