Any progress on 0.20 release?

Thx

> On Mar 12, 2018, at 5:28 PM, Renan DelValle <re...@apache.org> wrote:
> 
> Changing my vote to a -1 and closing the vote as failed.
> 
> Based on Stephan's experience, I went back and retested, and found a
> different error than Stephan found when running the integration tests:
> 
>               Executing tasks in goals: gen -> pyprep -> test
> 17:13:42 00:01   [gen]
> 17:13:42 00:01     [thrift-py]
> 17:13:42 00:01       [cache]
>                   No cached artifacts for 4 targets.
>                   Invalidated 4 targets.....
> 17:13:42 00:01   [pyprep]
> 17:13:42 00:01     [interpreter]
> 17:13:46 00:05     [requirements]
> 17:13:46 00:05       [cache]
>                   No cached artifacts for 37 targets.
>                   Invalidated 37 targets.
> 17:14:06 00:25     [sources]
>               Waiting for background workers to finish.
> 17:14:06 00:25   [complete]
>               FAILURE
> Exception caught: (<type 'exceptions.IOError'>)
> 
> Exception message: [Errno 36] File name too long:
> u'/home/user/aurora/.pants.d/build_invalidator/7/pants_
> backend_python_tasks2_gather_sources_GatherSources/.pants.
> d.gen.thrift-py.252d64521cf9.api.src.main.thrift.org.
> apache.aurora.gen._storage.current.api.src.main.thrift.
> org.apache.aurora.gen._storage.hash'
> 
> Filed https://issues.apache.org/jira/browse/AURORA-1980 for this issue.
> 
> Stephan, if you could, please file the issues for the failures you've seen
> so we can track them.
> 
> 
> -Renan
> 
> 
> On Mon, Mar 12, 2018 at 3:14 PM, Stephan Erb <stephan....@blue-yonder.com>
> wrote:
> 
>> Unfortunately, I am unable to get the end-to-end tests to pass, even after
>> a full `vagrant destroy && git clean -xfd`.
>> 
>> Things I have seen fail:
>> 
>> • Failures of the curl disabling Mesos maintenance schedules
>> • Can't check signature: public key not found
>> 
>> I have tested on two different computers to rule out a bad setup, but both
>> errors have shown up a couple of times now. Could it be that the Vagrant
>> update has introduced some issues here?
>> 
>> 
>> On 07.03.18, 21:44, "Renan DelValle" <re...@apache.org> wrote:
>> 
>>    Reminder that the vote for 0.20.0 is still open.
>> 
>>    Kicking off the vote with a +1 from me.
>> 
>>    On Thu, Mar 1, 2018 at 4:39 PM, Renan DelValle <re...@apache.org>
>> wrote:
>> 
>>> All,
>>> 
>>> I propose that we accept the following release candidate as the
>> official
>>> Apache Aurora 0.20.0 release.
>>> 
>>> Aurora 0.20.0-rc0 includes the following:
>>> ---
>>> The RELEASE NOTES for the release are available at:
>>> https://git-wip-us.apache.org/repos/asf?p=aurora.git&f=
>>> RELEASE-NOTES.md&hb=rel/0.20.0-rc0
>>> 
>>> The CHANGELOG for the release is available at:
>>> https://git-wip-us.apache.org/repos/asf?p=aurora.git&f=
>>> CHANGELOG&hb=rel/0.20.0-rc0
>>> 
>>> The tag used to create the release candidate is:
>>> https://git-wip-us.apache.org/repos/asf?p=aurora.git;a=
>>> shortlog;h=refs/tags/rel/0.20.0-rc0
>>> 
>>> The release candidate is available at:
>>> https://dist.apache.org/repos/dist/dev/aurora/0.20.0-rc0/
>>> apache-aurora-0.20.0-rc0.tar.gz
>>> 
>>> The MD5 checksum of the release candidate can be found at:
>>> https://dist.apache.org/repos/dist/dev/aurora/0.20.0-rc0/
>>> apache-aurora-0.20.0-rc0.tar.gz.md5
>>> 
>>> The signature of the release candidate can be found at:
>>> https://dist.apache.org/repos/dist/dev/aurora/0.20.0-rc0/
>>> apache-aurora-0.20.0-rc0.tar.gz.asc
>>> 
>>> The GPG key used to sign the release are available at:
>>> https://dist.apache.org/repos/dist/dev/aurora/KEYS
>>> 
>>> Please download, verify, and test.
>>> 
>>> The vote will close on Sun Mar  4 16:35:59 PST 2018
>>> 
>>> [ ] +1 Release this as Apache Aurora 0.20.0
>>> [ ] +0
>>> [ ] -1 Do not release this as Apache Aurora 0.20.0 because...
>>> 
>> 
>> 
>> 

Reply via email to