Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

2018-10-24 Thread Sean McGinnis 
On Wed, Oct 24, 2018 at 12:08 AM Tony Breeds 
wrote:

> On Wed, Oct 24, 2018 at 03:23:53AM +, 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
>
> 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/release/release-openstack-python3/e84da68/job-output.txt.gz#_2018-10-24_03_20_15_264676
> ___
> Release-job-failures mailing list
> release-job-failu...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
>
__
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

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

2018-10-24 Thread Jeremy Stanley 
On 2018-10-24 16:08:26 +1100 (+1100), Tony Breeds wrote:
> On Wed, Oct 24, 2018 at 03:23:53AM +, 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


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

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

2018-10-24 Thread Thierry Carrez 

Tony Breeds wrote:

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


Yes the release is up on Pypi and on releases.o.o, so I think we are good.


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.


The timestamps don't match, but in the logs the tar.gz is uploaded last, 
as designed... Where did you get the timestamps from ? If from Pypi 
maybe their clocks are off or they do some kind of processing that 
affects the timestamp...


--
Thierry Carrez (ttx)

__
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

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

2018-10-23 Thread Tony Breeds 
On Wed, Oct 24, 2018 at 03:23:53AM +, 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

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/release/release-openstack-python3/e84da68/job-output.txt.gz#_2018-10-24_03_20_15_264676


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

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

2018-10-19 Thread Andreas Jaeger 

On 19/10/2018 16.19, Sean McGinnis wrote:
This appears to be another in-transit job conflict with the py3 work. 
Things should be fine, but we will need to manually propose the 
constraint update since it was skipped.


On Fri, Oct 19, 2018, 09:14 > wrote:


Build failed.

- release-openstack-python3

http://logs.openstack.org/33/33d839da8acb93a36a45186d158262f269e9bbd6/release/release-openstack-python3/1cb87ba/
: SUCCESS in 2m 44s
- announce-release announce-release : SKIPPED
- propose-update-constraints propose-update-constraints : SKIPPED
- release-openstack-python

http://logs.openstack.org/33/33d839da8acb93a36a45186d158262f269e9bbd6/release/release-openstack-python/3a9339d/
: POST_FAILURE in 2m 40s


We're not using tox venv anymore for the release job, so I think we need 
to remove the "fetch-tox-output" role completely:


https://review.openstack.org/611886

Andreas



___
Release-job-failures mailing list
release-job-failu...@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures


__
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




--
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

2018-10-19 Thread Sean McGinnis 
This appears to be another in-transit job conflict with the py3 work.
Things should be fine, but we will need to manually propose the constraint
update since it was skipped.

On Fri, Oct 19, 2018, 09:14  wrote:

> Build failed.
>
> - release-openstack-python3
> http://logs.openstack.org/33/33d839da8acb93a36a45186d158262f269e9bbd6/release/release-openstack-python3/1cb87ba/
> : SUCCESS in 2m 44s
> - announce-release announce-release : SKIPPED
> - propose-update-constraints propose-update-constraints : SKIPPED
> - release-openstack-python
> http://logs.openstack.org/33/33d839da8acb93a36a45186d158262f269e9bbd6/release/release-openstack-python/3a9339d/
> : POST_FAILURE in 2m 40s
>
> ___
> Release-job-failures mailing list
> release-job-failu...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
>
__
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