You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the course of #23731, I wanted the CI to run a higher boto3 (resp. botocore) than before, and this breaks the construction of the s3_resource fixture, which then silently skips all tests, due to a
except: # noqa: flake8
pytest.skip("failure to use s3 resource")
While this is an upstream change/issue, we need to adapt the tests to find the right credentials, and - more pressingly - the travis-36 is the only job that tests boto, AFAICT.
In any case (notice, there's no pandas import, but this is what the constructor of s3_resource tries), this works:
Here's a more detailed view using boto3.set_stream_logger('botocore', level='DEBUG'). Seems that the new version has become more restrictive regarding credential discovery. I don't have experience with boto (the debug command was 1min of googling ;-)), but that shouldn't be too hard to set up, hopefully.
In the course of #23731, I wanted the CI to run a higher boto3 (resp. botocore) than before, and this breaks the construction of the
s3_resource
fixture, which then silently skips all tests, due to aWhile this is an upstream change/issue, we need to adapt the tests to find the right credentials, and - more pressingly - the
travis-36
is the only job that tests boto, AFAICT.In any case (notice, there's no pandas import, but this is what the constructor of
s3_resource
tries), this works:while with
botocore>=1.11
(which I need for testing #23731):Here's a more detailed view using
boto3.set_stream_logger('botocore', level='DEBUG')
. Seems that the new version has become more restrictive regarding credential discovery. I don't have experience with boto (the debug command was 1min of googling ;-)), but that shouldn't be too hard to set up, hopefully.Old version:
In the new version, the problem already starts upon connection, but only shows up when trying to interact with the resource:
The text was updated successfully, but these errors were encountered: