jonkeane commented on issue #14829:
URL: https://github.com/apache/arrow/issues/14829#issuecomment-1367506270

   We have some output in the test output, here's the error (and this is all 
for the 10.13 runners): 
   
   
https://github.com/ursacomputing/crossbow/actions/runs/3799336658/jobs/6461765126#step:7:10697
   
   ```
     Start test: install_pyarrow
     virtualenv: arrow-test
     Using virtual environment 'arrow-test' ...
     + '/Users/voltrondata/.virtualenvs/arrow-test/bin/python' -m pip install 
--upgrade --no-user --extra-index-url https://repo.fury.io/arrow-nightlies/ 
--pre --upgrade 'pyarrow'
     Looking in indexes: https://pypi.org/simple, 
https://repo.fury.io/arrow-nightlies/
     Requirement already satisfied: pyarrow in 
/Users/voltrondata/.virtualenvs/arrow-test/lib/python3.9/site-packages 
(10.0.0.dev211)
     Collecting pyarrow
       Downloading 
https://repo.fury.io/arrow-nightlies/-/ver_FFekQ/pyarrow-11.0.0.dev336.tar.gz 
(1.0 MB)
          ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.0/1.0 MB 9.9 MB/s eta 
0:00:00
       Installing build dependencies: started
       Installing build dependencies: finished with status 'done'
       Getting requirements to build wheel: started
       Getting requirements to build wheel: finished with status 'done'
       Preparing metadata (pyproject.toml): started
       Preparing metadata (pyproject.toml): finished with status 'done'
     Discarding 
https://repo.fury.io/arrow-nightlies/-/ver_FFekQ/pyarrow-11.0.0.dev336.tar.gz#md5=0ef59391d75d28053f5e899f824b3842
 (from https://repo.fury.io/arrow-nightlies/pyarrow/): Requested pyarrow from 
https://repo.fury.io/arrow-nightlies/-/ver_FFekQ/pyarrow-11.0.0.dev336.tar.gz#md5=0ef59391d75d28053f5e899f824b3842
 has inconsistent version: filename has '11.0.0.dev336', but metadata has 
'11.0.0a0'
       Downloading 
https://repo.fury.io/arrow-nightlies/-/ver_1ASXRV/pyarrow-11.0.0.dev334.tar.gz 
(1.0 MB)
          ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.0/1.0 MB 7.6 MB/s eta 
0:00:00
       Installing build dependencies: started
       Installing build dependencies: finished with status 'done'
       Getting requirements to build wheel: started
       Getting requirements to build wheel: finished with status 'done'
       Preparing metadata (pyproject.toml): started
       Preparing metadata (pyproject.toml): finished with status 'done'
     Discarding 
https://repo.fury.io/arrow-nightlies/-/ver_1ASXRV/pyarrow-11.0.0.dev334.tar.gz#md5=1c4676db5c0ef74a27bc307213c40b82
 (from https://repo.fury.io/arrow-nightlies/pyarrow/): Requested pyarrow from 
https://repo.fury.io/arrow-nightlies/-/ver_1ASXRV/pyarrow-11.0.0.dev334.tar.gz#md5=1c4676db5c0ef74a27bc307213c40b82
 has inconsistent version: filename has '11.0.0.dev334', but metadata has 
'11.0.0a0'
     ...
   ```
   
   I tried in #15112 to remove the virtual env that's being used (it looks like 
there's an already-installed version of pyarrow there), but that fails still 
with a similar error.  I'm suspicious about `has inconsistent version: filename 
has '11.0.0.dev334', but metadata has '11.0.0a0'` I can't seem to find where 
that `11.0.0a0` is coming from (it's not in the tar.gz and it's not in our 
source as far as I can tell. Eventually after looking at all of the hosted 
sources, it falls back to 10.0.1 
(https://github.com/ursacomputing/crossbow/actions/runs/3799336658/jobs/6461765126#step:9:10737)
 and then that fails to build from source.
   
   Ultimately, I suspect what's happening is that because we don't build 
pyarrow nightly binaries for 10.13 anymore (since 10.0.0dev222 if I'm looking 
at https://pypi.fury.io/arrow-nightlies/pyarrow correctly), this job won't work 
easily. Maybe we should skip our pyarrow tests for 10.13 (they will be skipped 
on cran already...)? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to