Hi Neal,

The flaky Flight auth test has been an issue recently:
https://issues.apache.org/jira/browse/ARROW-7721

I'm hoping to take a look at this when I get a chance.

Best,
David

On 2/3/20, Neal Richardson <neal.p.richard...@gmail.com> wrote:
> Some further color, as builds have started to fail:
>
> 1. Windows source fails oddly; it seems that installing boost makes wget
> not work correctly. Before installing boost, I can wget the rc tarball and
> build as far as the boost version check in C++, but after installing boost,
> I can't download the tarball.
> 2. On macOS, C# fails because it looks for a specific dotnet version that
> is not one of the 6 present. Skipping C#, python fails in cmake for not
> finding a CXX compiler:
> https://github.com/apache/arrow/runs/424318337?check_suite_focus=true#step:3:35613
> 3. On ubuntu source verification fails on Java, Flight memory leak:
> https://github.com/apache/arrow/runs/424357626#step:3:24982
> 4. Ubuntu wheels fail on python 3.5, but differently from Kou's experience:
> https://github.com/apache/arrow/runs/424357635#step:3:4162
>
> Not sure how much of this is misconfigured environment and how much is bad
> code.
>
> Neal
>
> On Mon, Feb 3, 2020 at 4:19 PM Neal Richardson
> <neal.p.richard...@gmail.com>
> wrote:
>
>> I've been experimenting with running the release verification on GitHub
>> Actions: https://github.com/apache/arrow/pull/6349. It would be great to
>> automate at least the core checks, even if releasing still requires some
>> manual checking too.
>>
>> So far, I've verified Python wheels on Windows except for python 3.8
>> (there's some issue with py38 vs. py38m) and I've made it through the C++
>> source build on macOS. Other jobs are either still running or need some
>> further debugging on the setup.
>>
>> If anyone wants to try to push these further, please feel free to push to
>> my branch.
>>
>> Neal
>>
>> On Mon, Feb 3, 2020 at 11:37 AM Neal Richardson <
>> neal.p.richard...@gmail.com> wrote:
>>
>>> I used that with
>>> https://patch-diff.githubusercontent.com/raw/apache/arrow/pull/6344.diff
>>> applied.
>>>
>>> On Mon, Feb 3, 2020 at 11:34 AM Krisztián Szűcs <
>>> szucs.kriszt...@gmail.com> wrote:
>>>
>>>> Please use the latest master [1] to verify the wheels.
>>>>
>>>> [1]:
>>>> https://github.com/apache/arrow/commit/cb81f7d84c26cd75f4568ae1b29744cb4218b578
>>>>
>>>> On Mon, Feb 3, 2020 at 8:26 PM Neal Richardson
>>>> <neal.p.richard...@gmail.com> wrote:
>>>> >
>>>> > +1 (non-binding)
>>>> >
>>>> > I did binary verification and macOS (10.14) wheels. Wheels for 3.5
>>>> failed
>>>> > as previously described, and 2.7 also failed similarly, so I'm
>>>> gathering
>>>> > that that's not a blocker. 3.6 - 3.8 passed once I added this patch
>>>> > for
>>>> > Flight test fixtures: https://github.com/apache/arrow/pull/6345
>>>> >
>>>> > Neal
>>>> >
>>>> > On Mon, Feb 3, 2020 at 7:38 AM Antoine Pitrou <solip...@pitrou.net>
>>>> wrote:
>>>> >
>>>> > > On Fri, 31 Jan 2020 04:13:12 +0100
>>>> > > Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote:
>>>> > > > Hi,
>>>> > > >
>>>> > > > I would like to propose the following release candidate (RC2) of
>>>> Apache
>>>> > > > Arrow version 0.16.0. This is a release consisting of 728
>>>> > > > resolved JIRA issues[1].
>>>> > > >
>>>> > > > This release candidate is based on commit:
>>>> > > > 729a7689fd87572e6a14ad36f19cd579a8b8d9c5 [2]
>>>> > > >
>>>> > > > The source release rc2 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.
>>>> > > >
>>>> > > > The vote will be open for at least 72 hours.
>>>> > > >
>>>> > > > [ ] +1 Release this as Apache Arrow 0.16.0
>>>> > > > [ ] +0
>>>> > > > [ ] -1 Do not release this as Apache Arrow 0.16.0 because...
>>>> > >
>>>> > > +1 from me.
>>>> > >
>>>> > > Regards
>>>> > >
>>>> > > Antoine.
>>>> > >
>>>> > >
>>>> > >
>>>>
>>>
>

Reply via email to