[bot-automerge] google-cloud-cpp v2.21.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• [ ] Dependencies have been updated if changed: see upstream
• [ ] Tests have passed
• [ ] Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. 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 code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Closes: #146

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
google-cloud-cpp	2.21.0

Dependency Analysis

We couldn't run dependency analysis due to an internal error in the bot, depfinder, or grayskull. :/ Help is very welcome!

_{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/cf-scripts/actions/runs/7881946535, please use this URL for debugging.}

[conda-forge-webservices[bot]]

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[bot]]

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.

[github-actions[bot]]

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

It appears that not all commits to this PR were made by the bot. Thus this PR is not being automatically merged. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[h-vetinari]

@coryan, it looks like we're already back in danger territory here. 😑

Windows builds have timed out 2 out of 2 times, while one out of 6 linux runs timed out (3 arches x 2 runs), with another one getting very close at ~5:45h. I've started the third run now.

[coryan]

@coryan, it looks like we're already back in danger territory here. 😑

Ugh, that was much faster than I expected.

Windows builds have timed out 2 out of 2 times, while one out of 6 linux runs timed out (3 arches x 2 runs), with another one getting very close at ~5:45h. I've started the third run now.

Would be nice to have something like mozilla/sccache configured, so the previous work is not lost. But I digress.

I will collect data on the remaining features and look for a split that gives us more headroom.

I will also discuss techniques to reduce the build times in the project.

[coryan]

I found a bug in the Windows build: #163 I think we should fix the v2.17.0 packages and then upgrade, but I am guessing as to what would work better in Conda.

[h-vetinari]

Would be nice to have something like mozilla/sccache configured, so the previous work is not lost. But I digress.

That would be amazing, but quite hard to pull off I think. If you have more than just idly curious interest in this, you can open an issue under https://github.com/conda-forge/conda-forge.github.io to discuss how we might set this up - I don't foresee it to be easy though 😅

I found a bug in the Windows build: #163 I think we should fix the v2.17.0 packages and then upgrade, but I am guessing as to what would work better in Conda.

We haven't released 2.21 here yet, so that worked just fine. If we had already merged some newer version on main, what we do is create a maintenance branch (which also creates & publishes artefacts).

Ugh, that was much faster than I expected.

Well, the good news is that with #163 we should be getting roughly ~30min of saved time, and even without that it would still be feasible (for 2.21) - just needs a bit of patience with the restarts. However, given the rapid growth of google-cloud-cpp, it's good that you opened #164 already. 🙏