[bot-automerge] Rebuild for aws_c_io0135

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update aws_c_io0135.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/3312999934, please use this URL for debugging.}

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: failed

Thus the PR was not passing and not merged.

[h-vetinari]

Same error as in #75:

99% tests passed, 2 tests failed out of 647

Total Test time (real) =  60.50 sec

The following tests FAILED:
	638 - h2_sm_acquire_stream (Failed)
	639 - h2_sm_acquire_stream_multiple_connections (Failed)

[h-vetinari]

@xhochy

I think we should consider rolling back the aws_c_io0135 migration (i.e. deleting it in the pinning) until this PR is resolved (at least, if working through the various open migrations - incl. OpenSSL 3 - is a priority).

Currently everything seems to be stuck on this - the interaction of the three different migrations (aws_c_io0135, aws_c_common083, openssl) provides lots of different ways for feedstocks to deadlock each other if they don't move in sync on the migrators (which they often don't).

Current example - even with the backports we did, we're still running into issues in conda-forge/aws-sdk-cpp-feedstock#579, e.g.

The reported errors are:
- Encountered problems while solving:
-   - package aws-c-event-stream-0.2.15-h92b359b_1 requires aws-c-io >=0.13.4,<0.13.5.0a0, but none of the providers can be installed

[h-vetinari]

Alternative: we skip windows for now on this feedstock, which is not on the critical path for many of the other migrator PRs AFAICT.

[xhochy]

We are skipping tests on Linux 🙈 already, so we might also do this on Windows.

[xhochy]

@h-vetinari Any objections about skipping tests here? I don't feel that confident in working without tests but as we already doing this for Linux for a while, this is probably a sane way forward.

[h-vetinari]

No objection from my side, but also: I don't know this stack 😅

We could raise an issue upstream?

[regro-cf-autotick-bot]

I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. This was generated by https://github.com/regro/autotick-bot/actions/runs/3348739541