TST: failure on s3 mocking

[jreback]

master seems to fail recently: https://travis-ci.org/pandas-dev/pandas/jobs/367585545

on pandas/tests/iotest_parquet.py -k s3.

works locally for me. very odd as this is mocked and shouldn't ever have a connection error.

In particular xfailing: 336fba7

• test_read_csv_chunked_download in pandas.tests.io.test_network.py
• test_s3_roundtrip for fp & pyarrow in pandas.testsio.test_parquet.py

[jreback]

@TomAugspurger any idea?

[TomAugspurger]

cc @martindurant, have you been dealing with moto / requests issues recently?

I think getmoto/moto#1026 is the one.

[martindurant]

The referenced issue causes anything based on requests to fail following the use of moto in some cases. In this particular case, though, the test is using moto, right?

The following fixed the problem with requests: https://github.com/dask/dask/blob/master/dask/bytes/tests/test_s3.py#L46

[spulec]

Hi all; I'm one of the maintainers of Moto.

Our most recent version had a regex bug in catching certain S3 urls to patch. We are releasing a new version in the next couple minutes that should resolve any issues (1.3.3).

Feel free to ping me if these issues don't seem to go away.

[jreback]

thanks @spulec!

[TomAugspurger]

Thanks @spulec, I can confirm that upgrading to 1.3.3 fixed things for me locally!

We still have some failures on our CI, though I think that this is fully pandas problem now: https://travis-ci.org/TomAugspurger/pandas/jobs/369087870.

The potential problem, we're mixing pip & conda installs in various orders, so our env looks like

boto                      2.48.0                    <pip>
boto3                     1.7.5                     <pip>
boto3                     1.7.4                    py27_0  
botocore                  1.10.5                    <pip>
botocore                  1.10.4                   py27_0  

So who knows which versions are active. Cleaning that up now.

[spulec]

Okay, let me know if it does end up pointing back to Moto.

[csolamx]

Hi @spulec! I installed 1.3.5 today and it seems that it's mocking any requests not belonging to AWS. Are there other updates to consider or workarounds?

Thanks!