Got it, thank you for clarifying. It wasn't clear whether the bug
would occur in the build environment (CentOS 5 + devtoolset-2) as well
as other Linux environments.
On Wed, Oct 17, 2018 at 4:16 PM Antoine Pitrou <anto...@python.org> wrote:
>
>
> Le 17/10/2018 à 20:38, Wes McKinney a écrit :
> > hi folks,
> >
> > Since the Python wheels are being installed 10,000 times per day or
> > more, I don't think we should allow them to be broken for much longer.
> >
> > What additional patches need to be done before an RC can be cut? Since
> > I'm concerned about the broken patches undermining the project's
> > reputation, I can adjust my priorities to start a release vote later
> > today or first thing tomorrow morning. Seems like
> > https://issues.apache.org/jira/browse/ARROW-3535 might be the last
> > item, and I can prepare a maintenance branch with the cherry-picked
> > fixes
> >
> > Was there a determination as to why our CI systems did not catch the
> > blocker ARROW-3514?
>
> Because it was not exercised by the test suite. My take is that the bug
> would only happen with specific data, e.g. tiny and/or entirely
> incompressible. I don't think general gzip compression of Parquet files
> was broken.
>
> Regards
>
> Antoine.
