CI/TST: Skip another s3 test that can crash GHA worker
State: closed

Example from https://github.com/pandas-dev/pandas/runs/4957463823?check_suite_focus=true

```
.....ss...s...s.........sss..........ss..........ss..................ssssss...s...s...x.............................XXXXXXXXX.XxXX2022-01-26 21:25:12,489 - s3fs - DEBUG - Setting up s3fs instance
2022-01-26T21:25:12.5442600Z 2022-01-26 21:25:12,543 - s3fs - DEBUG - Get directory listing page for pandas-test
2022-01-26T21:25:12.5650735Z 2022-01-26 21:25:12,564 - s3fs - DEBUG - Fetch: pandas-test/large-file.csv, 0-5505024
2022-01-26T22:08:22.5747205Z ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
2022-01-26T22:08:23.3842467Z 
```


Labels:
name: Testing
description: pandas testing functions or related to the test suite
name: CI
description: Continuous Integration
name: IO Network
description: Local or Cloud (AWS, GCS, etc.) IO Issues

Comments:
Appears to also happen for `test_user_agent.py` so skipping as well

```
2022-01-27T01:05:08.3878329Z ...................................127.0.0.1 - - [27/Jan/2022 01:05:07] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:08.5454000Z ......................................127.0.0.1 - - [27/Jan/2022 01:05:08] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:09.2164525Z .................................127.0.0.1 - - [27/Jan/2022 01:05:09] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:09.9411631Z ..................................127.0.0.1 - - [27/Jan/2022 01:05:09] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:10.4353956Z .................127.0.0.1 - - [27/Jan/2022 01:05:10] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:11.0281578Z .........................127.0.0.1 - - [27/Jan/2022 01:05:11] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:11.7202508Z .................................127.0.0.1 - - [27/Jan/2022 01:05:11] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:12.2688780Z ...............127.0.0.1 - - [27/Jan/2022 01:05:12] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:12.7840837Z .............127.0.0.1 - - [27/Jan/2022 01:05:12] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:13.5826589Z ............................127.0.0.1 - - [27/Jan/2022 01:05:13] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:14.1037063Z .......127.0.0.1 - - [27/Jan/2022 01:05:14] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:14.6141578Z 127.0.0.1 - - [27/Jan/2022 01:05:14] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:15.1163350Z 127.0.0.1 - - [27/Jan/2022 01:05:15] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:15.6335235Z .127.0.0.1 - - [27/Jan/2022 01:05:15] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:16.3507605Z ...........................127.0.0.1 - - [27/Jan/2022 01:05:16] "GET / HTTP/1.1" 200 -
2022-01-27T01:05:16.8827726Z .x....127.0.0.1 - - [27/Jan/2022 01:05:16] "GET / HTTP/1.1" 200 -
2022-01-27T01:54:41.2645176Z ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
2022-01-27T01:54:43.1456377Z 
```
Fastparquet was fixed on 310 so adding that here too: https://github.com/dask/fastparquet/pull/739
Greenish-er.
@meeseeksdev backport 1.4.x
Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 1.4.x
git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
git cherry-pick -m1 20d096408afbdf0ca18638b88fb34026b5498ba7
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
git commit -am 'Backport PR #45651: CI/TST: Skip another s3 test that can crash GHA worker'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-45651-on-1.4.x
```

5. Create a PR against branch 1.4.x, I would have named this PR:

> "Backport PR #45651 on branch 1.4.x (CI/TST: Skip another s3 test that can crash GHA worker)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                
Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 1.4.x
git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
git cherry-pick -m1 20d096408afbdf0ca18638b88fb34026b5498ba7
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
git commit -am 'Backport PR #45651: CI/TST: Skip another s3 test that can crash GHA worker'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-45651-on-1.4.x
```

5. Create a PR against branch 1.4.x, I would have named this PR:

> "Backport PR #45651 on branch 1.4.x (CI/TST: Skip another s3 test that can crash GHA worker)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                
Actually I think this is okay not to backport