Carlos O'Ryan

This has been diagnosed as a GCC / libstd++ bug, see: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105329 I figured this out by reading: https://github.com/google/benchmark/issues/1398 I think the best thing to do in the `google-cloud-cpp`...

I think our build environment is overly complicated. We are installing both the IDE and the command-line version of the compiler. We then use the IDE paths: https://github.com/googleapis/google-cloud-cpp/blob/4bb4dec40d5af0e8bc4fa81a99fe0c3084fdce79/ci/kokoro/windows/build.bat#L29 We can...

## WIP ## Install on GCE Instance ``` curl -SL --output vs_buildtools.exe https://aka.ms/vs/17/release/vs_buildtools.exe start /w vs_buildtools.exe --quiet --wait --norestart --nocache --installpath "%ProgramFiles(x86)%\Microsoft Visual Studio\2022\BuildTools" --includeRecommended --add Microsoft.VisualStudio.Workload.VCTools --add Microsoft.VisualStudio.Component.VC.CLI.Support start...

## Problem The Kokoro build images install both the IDE and the command-line tools (which Microsoft calls "Build Tools") for MSVC 2017, 2019, and 2022. This is more than what...

## Notes We are still using `chocolatey` for some build tools, we need to use `choco upgrade -y all` when updating the image. We need to run `gcloud components update`...

This is now fixed.

Tested today and the problems are still there.

Tested again, the problems are still there.

No repeats in over 90d, closing

* GCB: https://console.cloud.google.com/cloud-build/builds;region=us-east1/94e09ac3-4450-42b0-9aaa-a72ec6afa61d;tab=detail?project=cloud-cpp-testing-resources * Raw: https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/main/2bb2d0203cb626553a6ae88e9490b93bd5e7685f/fedora-36-integration-daily/log-94e09ac3-4450-42b0-9aaa-a72ec6afa61d.txt