Formally we have
https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates.

You can help just by trying out the software and reporting any issues
you find based on the apache-arrow-0.12.0 tag that's in GitHub now

On Sun, Jan 13, 2019 at 7:23 PM Andrew Palumbo <[email protected]> wrote:
>
> I'd like to offer to help out with testing the RC, tomorrow, if needed. I 
> have specific needs for pyarrow, so can focus there, but other areas of 
> testing as well.
>
> Is there an RC from a commit? or should I continue working off of master?
>
> Thanks.
>
> --Andy
> ________________________________
> From: Andrew Palumbo <[email protected]>
> Sent: Sunday, January 13, 2019 8:14 PM
> To: [email protected]
> Subject: Re: pyarrow build errors
>
> fyi- as well that was from outside of any virtualenv, and using
>
> /arrow/cpp$ cmake --version
> cmake version 3.5.1
>
>
> ________________________________
> From: Andrew Palumbo <[email protected]>
> Sent: Sunday, January 13, 2019 8:11 PM
> To: [email protected]
> Subject: Re: pyarrow build errors
>
> FYI using the github/arrow/cpp/readme.md instructions, I just had a crash at:
>
>
> [ 50%] Building CXX object 
> src/parquet/CMakeFiles/parquet_objlib.dir/util/memory.cc.o
> [ 50%] Built target parquet_objlib
> Scanning dependencies of target parquet_shared
> [ 51%] Linking CXX shared library ../../build/release/libparquet.so
> [ 51%] Built target parquet_shared
> Scanning dependencies of target googletest_ep
> [ 52%] Creating directories for 'googletest_ep'
> [ 52%] Performing download step (download, verify and extract) for 
> 'googletest_ep'
> -- googletest_ep download command succeeded.  See also 
> /home/apalumbo/arrow/cpp/googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-download-*.log
> [ 53%] No patch step for 'googletest_ep'
> [ 53%] No update step for 'googletest_ep'
> [ 53%] Performing configure step for 'googletest_ep'
> -- googletest_ep configure command succeeded.  See also 
> /home/apalumbo/arrow/cpp/googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-configure-*.log
> [ 53%] Performing build step for 'googletest_ep'
> -- googletest_ep build command succeeded.  See also 
> /home/apalumbo/arrow/cpp/googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-build-*.log
> [ 53%] Performing install step for 'googletest_ep'
> -- googletest_ep install command succeeded.  See also 
> /home/apalumbo/arrow/cpp/googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-install-*.log
> [ 53%] Completed 'googletest_ep'
> [ 53%] Built target googletest_ep
> Scanning dependencies of target arrow_testing_objlib
> [ 54%] Building CXX object 
> src/arrow/CMakeFiles/arrow_testing_objlib.dir/test-util.cc.o
> [ 54%] Built target arrow_testing_objlib
> Scanning dependencies of target arrow_testing_shared
> [ 54%] Linking CXX shared library ../../build/release/libarrow_testing.so
> [ 54%] Built target arrow_testing_shared
> Scanning dependencies of target parquet-comparison-test
> [ 55%] Building CXX object 
> src/parquet/util/CMakeFiles/parquet-comparison-test.dir/comparison-test.cc.o
> [ 55%] Linking CXX executable ../../../build/release/parquet-comparison-test
> ../../../build/release/libparquet.so.12.0.0: undefined reference to 
> `boost::match_results<__gnu_cxx::__normal_iterator<char const*, std::string>, 
> std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, 
> std::string> > > 
> >::maybe_assign(boost::match_results<__gnu_cxx::__normal_iterator<char 
> const*, std::string>, 
> std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, 
> std::string> > > > const&)'
> ../../../build/release/libparquet.so.12.0.0: undefined reference to 
> `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, 
> std::string>, 
> std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, 
> std::string> > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > 
> >::construct_init(boost::basic_regex<char, boost::regex_traits<char, 
> boost::cpp_regex_traits<char> > > const&, 
> boost::regex_constants::_match_flags)'
> collect2: error: ld returned 1 exit status
> src/parquet/util/CMakeFiles/parquet-comparison-test.dir/build.make:101: 
> recipe for target 'build/release/parquet-comparison-test' failed
> make[3]: *** [build/release/parquet-comparison-test] Error 1
> CMakeFiles/Makefile2:4822: recipe for target 
> 'src/parquet/util/CMakeFiles/parquet-comparison-test.dir/all' failed
> make[2]: *** [src/parquet/util/CMakeFiles/parquet-comparison-test.dir/all] 
> Error 2
> CMakeFiles/Makefile2:255: recipe for target 'CMakeFiles/unittest.dir/rule' 
> failed
> make[1]: *** [CMakeFiles/unittest.dir/rule] Error 2
> Makefile:238: recipe for target 'unittest' failed
> make: *** [unittest] Error 2
>
>
>
> I have not downgraded CMake yet.
> ________________________________
> From: Andrew Palumbo <[email protected]>
> Sent: Sunday, January 13, 2019 8:08 PM
> To: [email protected]
> Subject: Re: pyarrow build errors
>
> Thanks Wes,
>
> I'd completely missed that, I'll ensure CMake 3.5 (this is a provisioned 
> Ubuntu 16.04 I should have mentioned).
>
> willdo. for the next round of building.
>
> I just blew out all of the repos and started from scratch with the 
> instructions from:
>
> https://github.com/apache/arrow/tree/master/cpp
>
> And the build seems to be going well currently.
>
> I'll check again with the CMake downgrade.   Though i believe that there is a 
> step in that piece of documentation which suggests upgrading with:
>
> `pip install cmake`
>
> which i did in the virtualenv.
>
> If your cmake version is too old on Linux, you could get a newer one via pip 
> install cmake.
>
>
> https://arrow.apache.org/docs/python/development.html#development
>
>
> Thanks,
>
> Andy
>
>
>
>
>
> ________________________________
> From: Wes McKinney <[email protected]>
> Sent: Sunday, January 13, 2019 7:40 PM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: pyarrow build errors
>
> hi Andy,
>
> This would indicate a problem with your environment -- this would
> affect any project that uses CMake and not only Arrow. It looks that
> you have multiple versions of CMake installed (3.5 and 3.13.2) and
> they are conflicting with each other. Ubuntu Xenial has CMake 3.5
>
> https://launchpad.net/ubuntu/xenial/+source/cmake
>
> I would suggest scrubbing your system of the other version of CMake
>
> - Wes
>
> On Sun, Jan 13, 2019 at 6:33 PM Andrew Palumbo <[email protected]> wrote:
> >
> > I understans that you are in the middle of a release, and I have been 
> > following along with builds of of different commits.  I am working off of 
> > master right now on an EC2/ubuntu linux, following instructions:
> >
> > https://arrow.apache.org/docs/python/parquet.html
> >
> > (pyarrow) [email protected]:~/repos$ pip install cmake
> > Looking in indexes: http://brk-saltmaster.ds.cylance.com:8080/simple, 
> > https://pypi.python.org/simple
> > Collecting cmake
> >   Downloading 
> > https://files.pythonhosted.org/packages/d2/58/dfb0a2010a538dbf9add2456b04579f1b0f91e309687f761891d5007de81/cmake-3.13.2.post1-cp27-cp27mu-manylinux1_x86_64.whl
> >  (15.9MB)
> >     100% |████████████████████████████████| 15.9MB 2.7MB/s
> > Installing collected packages: cmake
> > Successfully installed cmake-3.13.2.post1
> > (pyarrow) apalumbo@ip-10-25-4-180:~/repos$ pushd arrow/cpp/build
> > ~/repos/arrow/cpp/build ~/repos
> > (pyarrow) apalumbo@ip-10-25-4-180:~/repos/arrow/cpp/build$ cmake 
> > -DCMAKE_BUILD_TYPE=$ARROW_BUILD_TYPE \
> > >       -DCMAKE_INSTALL_PREFIX=$ARROW_HOME \
> > >       -DARROW_PARQUET=on \
> > >       -DARROW_PYTHON=on \
> > >       -DARROW_PLASMA=on \
> > >       -DARROW_BUILD_TESTS=OFF \
> > >       ..
> > CMake Error: Could not find CMAKE_ROOT !!!
> > CMake has most likely not been installed correctly.
> > Modules directory not found in
> > /home/apalumbo/pyarrow/share/cmake-3.5
> > CMake Error: Error executing cmake::LoadCache(). Aborting.
> >
> > I've set all environment builds, however I have not had any luck this last 
> > week (off of different commits)
> >
> > I will blow out the enfronment and start fresh again.  Wanted to make you 
> > aware.
> >
> > Thanks very much,
> >
> > Andy

Reply via email to