Build failed. - release-openstack-python3 http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/releas... : POST_FAILURE in 2m 18s - announce-release http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/releas... : SUCCESS in 2m 21s - propose-update-constraints http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/releas... : SUCCESS in 3m 05s - release-openstack-python http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/releas... : SUCCESS in 2m 15s
On Wed, Oct 24, 2018 at 03:23:53AM +0000, zuul@openstack.org wrote:
Build failed.
- release-openstack-python3 http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/releas... : 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 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. [1] http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/releas...
On Wed, Oct 24, 2018 at 12:08 AM Tony Breeds <tony@bakeyournoodle.com> wrote:
On Wed, Oct 24, 2018 at 03:23:53AM +0000, zuul@openstack.org wrote:
Build failed.
- release-openstack-python3 http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/releas... : 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
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 release-openstack-python3 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.
[1] http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/releas... _______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
participants (3)
-
Sean McGinnis
-
Tony Breeds
-
zuul@openstack.org