html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/pull/3162#issuecomment-516645837,https://api.github.com/repos/pydata/xarray/issues/3162,516645837,MDEyOklzc3VlQ29tbWVudDUxNjY0NTgzNw==,1217238,2019-07-31T00:28:53Z,2019-07-31T00:28:53Z,MEMBER,Thanks @scottyhq !,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,473142248
https://github.com/pydata/xarray/pull/3162#issuecomment-515625123,https://api.github.com/repos/pydata/xarray/issues/3162,515625123,MDEyOklzc3VlQ29tbWVudDUxNTYyNTEyMw==,1217238,2019-07-26T23:09:54Z,2019-07-26T23:10:04Z,MEMBER,"The build is already green because this is marked as an allowed failure, but it shows up in the list of failing tests anyways. It's a little  confusing but that was the best way I found to make the result of these tests noticeable without counting as a build failure.

If you click on ""Checks"" at the top of this PR and then click on the top level ""pydata.xarray"" section of Azure, you see the full details on why the test is failing still:
```
self = <xarray.tests.test_backends.TestRasterio object at 0x7fb4b5cfa358>

    @network
    def test_rasterio_vrt_network(self):
        # Make sure loading w/ rasterio give same results as xarray
        import rasterio
        # use same url that rasterio package uses in tests
        prefix = ""https://landsat-pds.s3.amazonaws.com/L8/139/045/""
        image = ""LC81390452014295LGN00/LC81390452014295LGN00_B1.TIF""
        httpstif = prefix + image
>       with rasterio.Env(aws_unsigned=True):

xarray/tests/test_backends.py:3797: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/share/miniconda/envs/xarray-tests/lib/python3.6/site-packages/rasterio/env.py:193: in __init__
    aws_unsigned=aws_unsigned)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <rasterio.session.AWSSession object at 0x7fb4b4b10da0>, session = None
aws_unsigned = True, aws_access_key_id = None, aws_secret_access_key = None
aws_session_token = None, region_name = None, profile_name = None
requester_pays = False

    def __init__(
            self, session=None, aws_unsigned=False, aws_access_key_id=None,
            aws_secret_access_key=None, aws_session_token=None,
            region_name=None, profile_name=None, requester_pays=False):
        """"""Create a new boto3 session
    
        Parameters
        ----------
        session : optional
            A boto3 session object.
        aws_unsigned : bool, optional (default: False)
            If True, requests will be unsigned.
        aws_access_key_id : str, optional
            An access key id, as per boto3.
        aws_secret_access_key : str, optional
            A secret access key, as per boto3.
        aws_session_token : str, optional
            A session token, as per boto3.
        region_name : str, optional
            A region name, as per boto3.
        profile_name : str, optional
            A shared credentials profile name, as per boto3.
        requester_pays : bool, optional
            True if the requester agrees to pay transfer costs (default:
            False)
        """"""
>       import boto3
E       ModuleNotFoundError: No module named 'boto3'
```

It looks like using the `aws_unsigned` argument means that boto3 is required, but we don't have that installed in our CI currently. It would be straightforward to add it whenever we install rasterio -- put it in the lists in `ci/requirements/`","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,473142248