Hi, > I was verifying RC2. Seems that commit was not included in RC2. > > ~/arrow$ git log | grep be663c14637b2bdfef935946b6e91b6317219332 > ~/arrow$ > > So maybe this is the culprit?
Yes. The commit was pushed after RC2. Thanks for verifying RC2. We'll release RC3. I hope that you verify RC3 too. -- kou In <cy4pr06mb2773aab37b892aac260c6ff394...@cy4pr06mb2773.namprd06.prod.outlook.com> "Re: [VOTE] Release Apache Arrow 0.12.0 (RC2) ARROW" on Tue, 15 Jan 2019 17:42:57 +0000, Andrew Palumbo <ap....@outlook.com> wrote: > Wes, > /tmp doesnt seem to be the issue. it seems this machine has ~295 G. (I'll > try to eye-verify that there is not some massive memory leak a bit later, > seems unlikely though). > > ~$ df -Th /tmp > Filesystem Type Size Used Avail Use% Mounted on > /dev/xvda1 ext4 291G 4.6G 287G 2% / > > > > > Kouhei, > I was verifying RC2. Seems that commit was not included in RC2. > > ~/arrow$ git log | grep be663c14637b2bdfef935946b6e91b6317219332 > ~/arrow$ > > > So maybe this is the culprit? > > > > > I see that this commit is in master (from my local after a `git pull origin > master`): > > $ git log | grep -A20 be663c14637b2bdfef935946b6e91b6317219332 > commit be663c14637b2bdfef935946b6e91b6317219332 > Author: Kouhei Sutou <k...@clear-code.com> > Date: Sun Jan 13 11:14:51 2019 +0100 > > ARROW-4247: [Release] Update verify script for 0.12.0 > > * C++: -DARROW_GPU -> -DARROW_CUDA > * C++: Enable Gandiva > * C++: default: -DARROW_BUILD_TESTS=ON -> OFF > * Ruby: red-plasma, red-gandiva and red-parquet are added > * Rust: The top-level Cargo.toml is a virtual manifest > > Author: Kouhei Sutou <k...@clear-code.com> > > Closes #3389 from kou/release-update-verify-script and squashes the > following commits: > > f019a3fc <Kouhei Sutou> Update verify script for 0.12.0 > > > Thanks Very Much, > > Andy > > ________________________________ > From: Wes McKinney <wesmck...@gmail.com> > Sent: Tuesday, January 15, 2019 12:47 AM > To: dev@arrow.apache.org > Subject: Re: [VOTE] Release Apache Arrow 0.12.0 (RC2) ARROW > > I'm working on getting ARROW-4258 merged right now. ARROW-4260 also > should be fixed before another RC is cut > > https://issues.apache.org/jira/browse/ARROW-4260 > > On Mon, Jan 14, 2019 at 11:36 PM Kouhei Sutou <k...@clear-code.com> wrote: >> >> Hi, >> >> Does your verify-release-candidate.sh include >> https://github.com/apache/arrow/commit/be663c14637b2bdfef935946b6e91b6317219332 >> ? >> >> arrow-json-integration-test needs -DARROW_BUILD_TESTS=ON. >> >> >> Thanks, >> -- >> kou >> >> In >> <cy4pr06mb27732f2b6b14e508f44da68494...@cy4pr06mb2773.namprd06.prod.outlook.com> >> "Re: [VOTE] Release Apache Arrow 0.12.0 (RC2) ARROW" on Tue, 15 Jan 2019 >> 02:30:13 +0000, >> Andrew Palumbo <ap....@outlook.com> wrote: >> >> > After following all setup and install steps from: >> > https://cwiki.apache.org/confluence/display/ARROW/How+to+Verify+Release+Candidates >> > >> > >> > apalumbo@ip-xxx-xxx-xxx-xxx:~/arrow/dev/release$ >> > verify-release-candidate.sh source 0.12.0 2 >> > >> > >> > >> > fails with this stack trace: >> > >> > >> > >> > >> > ######################################################### >> > C++ producing, C++ consuming >> > ########################################################## >> > ========================================================== >> > Testing file >> > /tmp/arrow-0.12.0.5xTVS/apache-arrow-0.12.0/integration/data/simple.json >> > ========================================================== >> > -- Creating binary inputs >> > Traceback (most recent call last): >> > File "integration_test.py", line 1216, in <module> >> > run_all_tests(debug=args.debug, tempdir=args.tempdir) >> > File "integration_test.py", line 1179, in run_all_tests >> > runner.run() >> > File "integration_test.py", line 937, in run >> > self._compare_implementations(producer, consumer) >> > File "integration_test.py", line 959, in _compare_implementations >> > producer.json_to_file(json_path, producer_file_path) >> > File "integration_test.py", line 1086, in json_to_file >> > return self._run(arrow_path, json_path, 'JSON_TO_ARROW') >> > File "integration_test.py", line 1080, in _run >> > run_cmd(cmd) >> > File "integration_test.py", line 87, in run_cmd >> > output = subprocess.check_output(cmd, stderr=subprocess.STDOUT) >> > File >> > "/tmp/arrow-0.12.0.5xTVS/apache-arrow-0.12.0/test-miniconda/envs/arrow-test/lib/python3.6/subprocess.py", >> > line 336, in chec >> > k_output >> > **kwargs).stdout >> > File >> > "/tmp/arrow-0.12.0.5xTVS/apache-arrow-0.12.0/test-miniconda/envs/arrow-test/lib/python3.6/subprocess.py", >> > line 403, in run >> > with Popen(*popenargs, **kwargs) as process: >> > File >> > "/tmp/arrow-0.12.0.5xTVS/apache-arrow-0.12.0/test-miniconda/envs/arrow-test/lib/python3.6/subprocess.py", >> > line 709, in __in >> > it__ >> > restore_signals, start_new_session) >> > File >> > "/tmp/arrow-0.12.0.5xTVS/apache-arrow-0.12.0/test-miniconda/envs/arrow-test/lib/python3.6/subprocess.py", >> > line 1344, in _ex >> > ecute_child >> > raise child_exception_type(errno_num, err_msg, err_filename) >> > FileNotFoundError: [Errno 2] No such file or directory: >> > '/tmp/arrow-0.12.0.5xTVS/apache-arrow-0.12.0/cpp/build/release/arrow-json- >> > integration-test': >> > '/tmp/arrow-0.12.0.5xTVS/apache-arrow-0.12.0/cpp/build/release/arrow-json-integration-test' >> > + cleanup >> > + rm -fr /tmp/arrow-0.12.0.5xTVS >> > >> > >> > >> > >> > Jira or is this something obvious that i missed? >> > >> > Thank you. >> > >> > --Andy >> > >> > ________________________________ >> > From: Andrew Palumbo <andrew_palu...@msn.com> >> > Sent: Monday, January 14, 2019 9:23 PM >> > To: dev@arrow.apache.org >> > Subject: Re: [VOTE] Release Apache Arrow 0.12.0 (RC2) ARROW >> > >> > Hello, I've just run the verify scipt on the 0.12.0 tag after configuring >> > an Ubuntu machine per the instructions. I'm crashing at "c++ producing, >> > c++ consuming". With a no such file or directory... >> > Arrow-json-integration-test. >> > >> > When I was trying to build straight from that submodule there was a >> > >> > git submodule update --init command that I had to run. >> > >> > Just taking a wild guess that it could be the cause. >> > >> > I have to let this message go through to show the stack trace, because I >> > hadn't confirmed my dev@a.a.o acct.