Hi,

Thanks for verifying this RC.

> - failed to verify binaries
> 
> """
> + echo 'Failed to verify release candidate. See /tmp/arrow-0.14.0.gucvU
> for details.'
> Failed to verify release candidate. See /tmp/arrow-0.14.0.gucvU for details.
> """
> 
> There's no details in /tmp/arrow-0.14.0.gucvU. The script left a lot of
> zombie curl processes running...

It seems that one of curl downloads is failed.
Parallel download may be fragile.

https://github.com/apache/arrow/pull/4768 by Wes will solve
this situation. I've merged this.


> - failed to verify sources
> 
> """
> + export PATH
> /tmp/arrow-0.14.0.yum2X/apache-arrow-0.14.0/test-miniconda/etc/profile.d/conda.sh:
> line 55: PS1: unbound variable

https://github.com/apache/arrow/pull/4773 will solve this.
I added "set -u" to detect using undefined variables caused
by typo in
https://github.com/apache/arrow/commit/9a788dfc976035cabb0d4ab15f0f6fa306a5428d
.

It works well on my environment. But I understand that it's
not portable with shell script that sources external shell
script. (. $MINICONDA/etc/profile.d/conda.sh)

I've removed "set -u" by
https://github.com/apache/arrow/commit/9145c1591aedbd141454cfc7b6aad5190c0fb30e
.


Thanks,
--
kou

In <03cca1d7-7f8f-c46c-2360-132cd300c...@python.org>
  "Re: [VOTE] Release Apache Arrow 0.14.0 - RC0" on Mon, 1 Jul 2019 10:48:18 
+0200,
  Antoine Pitrou <anto...@python.org> wrote:

> 
> On Ubuntu 18.04:
> 
> - failed to verify binaries
> 
> """
> + echo 'Failed to verify release candidate. See /tmp/arrow-0.14.0.gucvU
> for details.'
> Failed to verify release candidate. See /tmp/arrow-0.14.0.gucvU for details.
> """
> 
> There's no details in /tmp/arrow-0.14.0.gucvU. The script left a lot of
> zombie curl processes running...
> 
> - failed to verify sources
> 
> """
> + export PATH
> /tmp/arrow-0.14.0.yum2X/apache-arrow-0.14.0/test-miniconda/etc/profile.d/conda.sh:
> line 55: PS1: unbound variable
> + ask_conda=
> + return 1
> + cleanup
> + '[' no = yes ']'
> + echo 'Failed to verify release candidate. See /tmp/arrow-0.14.0.yum2X
> for details.'
> Failed to verify release candidate. See /tmp/arrow-0.14.0.yum2X for details.
> """
> 
> There's no details in /tmp/arrow-0.14.0.yum2X
> 
> Regards
> 
> Antoine.
> 
> 
> 
> 
> 
> Le 01/07/2019 à 07:32, Sutou Kouhei a écrit :
>> Hi,
>> 
>> I would like to propose the following release candidate (RC0) of Apache
>> Arrow version 0.14.0. This is a release consiting of 618
>> resolved JIRA issues[1].
>> 
>> This release candidate is based on commit:
>> a591d76ad9a657110368aa422bb00f4010cb6b6e [2]
>> 
>> The source release rc0 is hosted at [3].
>> The binary artifacts are hosted at [4][5][6][7].
>> The changelog is located at [8].
>> 
>> Please download, verify checksums and signatures, run the unit tests,
>> and vote on the release. See [9] for how to validate a release candidate.
>> 
>> NOTE: You must use verify-release-candidate.sh at master.
>> I've fixed some problems after apache-arrow-0.14.0 tag.
>> C#'s "sourcelink test" is fragile. (Network related problem?)
>> It may be better that we add retry logic to "sourcelink test".
>> 
>> The vote will be open for at least 72 hours.
>> 
>> [ ] +1 Release this as Apache Arrow 0.14.0
>> [ ] +0
>> [ ] -1 Do not release this as Apache Arrow 0.14.0 because...
>> 
>> [1]: 
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%200.14.0
>> [2]: 
>> https://github.com/apache/arrow/tree/a591d76ad9a657110368aa422bb00f4010cb6b6e
>> [3]: https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-0.14.0-rc0
>> [4]: https://bintray.com/apache/arrow/centos-rc/0.14.0-rc0
>> [5]: https://bintray.com/apache/arrow/debian-rc/0.14.0-rc0
>> [6]: https://bintray.com/apache/arrow/python-rc/0.14.0-rc0
>> [7]: https://bintray.com/apache/arrow/ubuntu-rc/0.14.0-rc0
>> [8]: 
>> https://github.com/apache/arrow/blob/a591d76ad9a657110368aa422bb00f4010cb6b6e/CHANGELOG.md
>> [9]: 
>> https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates
>> 
>> 
>> Thanks,
>> --
>> kou
>> 

Reply via email to