[
https://issues.apache.org/jira/browse/ARROW-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565663#comment-16565663
]
Wes McKinney commented on ARROW-2959:
-------------------------------------
> Unless we're actually testing this
I think we should, in a nightly build
> Just to be clear, I personally am not going to invest time in bending over
> backwards to keep the script cross-undocumented-system compatible. I'm not
> going to stress out about keeping it that way for systems whose setup I have
> no way to reproduce.
Other developers will be responsible for reporting problems and helping fix
them. This is a shared responsibility and part of making sure Arrow runs in a
lot of places.
> I wasted a lot of time today only to figure out that the verification script
> can fail with a segfault when you are in a conda environment and have
> ARROW_HOME set. I don't think documenting this solves the problem, though it
> would have solved my immediate problem.
I wanted someone other than Uwe or me to suffer a bit as a release manager so
that more problems like these can be better documented and fixed. So what needs
to be said to prevent this particular issue is: "run this script in a clean,
unadulterated environment" (I know this from my past experience as an RM but I
didn't write this down)
> What is reasonable to me and what I think would solve the problem, is to
> provide a reliable way to set up each system we expect to be able to run on
> so that anyone can verify all supported platforms with minimal hassle.
There's way too many possibilities. The best we can do is test the primary
platforms (Ubuntu LTS releases, CentOS 6/7, Xcode 6.4 and higher, Windows MSVC
2015) and hope to catch more problems from users verifying the release on other
platforms. For example, running these platforms would not have caught the Arch
Linux issue that you reported from bleeding edge gcc.
Really all we are doing is cutting down on build/deploy problems that may occur
after a release is cut.
Docker would help with automated testing a release candidate on the common
platforms (Ubuntu, CentOS/RedHat/Fedora, Arch) but we still need to rely on
others to verify the release on their platform and report problems.
> Dockerize verify-release-candidate.{sh,bat}
> -------------------------------------------
>
> Key: ARROW-2959
> URL: https://issues.apache.org/jira/browse/ARROW-2959
> Project: Apache Arrow
> Issue Type: Task
> Components: C++, Packaging
> Affects Versions: 0.9.0
> Reporter: Phillip Cloud
> Priority: Major
>
> There are a number of issues with the linux version of this script that would
> disappear if the commands were all being run in a docker container.
> Anyone with docker installed should be able to verify the release candidate
> We could probably do the same for windows as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
