westonpace commented on PR #35255:
URL: https://github.com/apache/arrow/pull/35255#issuecomment-1544158180
> Do you think Appveyor should be fixed here? Any idea what the issue/fix is?
It would be nice to have at least one Windows CI job that uses GCS. I don't
know if the others do or not.
> Any idea what the issue/fix is?
Testbench is a standalone python project that emulates GCS. This is very
similar to how minio emulates S3. The C++ unit tests launch testbench (using
boost::process). Since testbench is a python project the C++ tests need to be
able to locate and run python. It appears, on Windows, this is not working.
Here is what the code to look for python looks like today:
```
std::vector<std::string> names{"python3", "python"};
// If the build script or application developer provides a value in the
PYTHON
// environment variable, then just use that.
if (const auto* env = std::getenv("PYTHON")) {
names = {env};
}
auto error = std::string(
"Could not start GCS emulator."
" Used the following list of python interpreter names:");
for (const auto& interpreter : names) {
auto exe_path = bp::search_path(interpreter);
error += " " + interpreter;
if (exe_path.empty()) {
error += " (exe not found)";
continue;
}
```
So maybe it's as easy as setting the `PYTHON` environment variable to point
to a valid python executable?
--
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]
