h-vetinari commented on issue #35587:
URL: https://github.com/apache/arrow/issues/35587#issuecomment-2495637658
Alright, with the backport of #44621, we're getting very close to enabling
the tests in conda-forge 🥳 - linux is now passing too, but there's now a new
failure on osx that won't go away even after multiple restarts:
```
[ RUN ] S3RegionResolutionTest.NonExistentBucket
[ FAILED ] S3RegionResolutionTest.NonExistentBucket (937852 ms)
$SRC_DIR/cpp/src/arrow/filesystem/s3fs_test.cc:381: Failure
Value of: maybe_region.status().message()
Expected: has substring "Bucket 'ursa-labs-nonexistent-bucket' not found"
Actual: "When resolving region for bucket 'ursa-labs-nonexistent-bucket':
AWS Error NETWORK_CONNECTION during HeadBucket operation: curlCode: 6, Could
not resolve hostname"
API: ListObjectsV2(bucket=nonexistent-bucket)
Time: 05:16:55 UTC 11/23/2024
DeploymentID: 58de1878-5055-4aeb-bee8-af6999751e71
RequestID: 180A8127F505A300
RemoteHost: 127.0.0.1
Host: 127.0.0.1:49361
UserAgent: aws-sdk-cpp/1.11.449 ua/2.0 md/aws-crt#0.29.5 os/Darwin/22.6.0
md/arch#x86_64 lang/c++#C++11 md/Clang#18.1.8 cfg/retry-mode#custom api/S3
Error: volume not found (cmd.StorageErr)
7: internal/logger/logonce.go:118:logger.(*logOnceType).logOnceIf()
6: internal/logger/logonce.go:149:logger.LogOnceIf()
5:
cmd/erasure-server-pool.go:1516:cmd.(*erasureServerPools).ListObjects()
4:
cmd/erasure-server-pool.go:1275:cmd.(*erasureServerPools).ListObjectsV2()
3:
cmd/bucket-listobjects-handlers.go:210:cmd.objectAPIHandlers.listObjectsV2Handler()
2:
cmd/bucket-listobjects-handlers.go:156:cmd.objectAPIHandlers.ListObjectsV2Handler()
1: net/http/server.go:2166:http.HandlerFunc.ServeHTTP()
```
This doesn't look like a serious failure to me, in the sense that `Could not
resolve hostname` points to some endpoint not being available (and it's only a
test about the failure case anyway, c.f. `'ursa-labs-nonexistent-bucket'`).
I can skip that one if desired, or does someone know of another way to fix
this?
@kou @pitrou @raulcd @assignUser
--
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]
