h-vetinari commented on PR #14832: URL: https://github.com/apache/arrow/pull/14832#issuecomment-1341428500
> But there is also a build for the same architecture with "-py3" suffix (which is also running the pyarrow tests). That seems a bit superfluous to run the python tests in each of the R builds as well? That's unavoidable without some surgery or splitting the feedstocks into `libarrow` and `pyarrow` - R only needs the former, but both get built by the same recipe. I can imagine trying to add a skip for the python bits based on some environment variable (e.g. if we detect `R_CONFIG`), but so far I've left things as-is (this is also how things were previously, with the difference that only one parrow version got built in the R jobs) -- 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]
