Skip to content

[infra] Backport: Ensure compatibility with the new custom kokoro win2019 image (#32649)#33052

Merged
veblush merged 2 commits intogrpc:v1.52.xfrom
eugeneo:release/fix-python
May 9, 2023
Merged

[infra] Backport: Ensure compatibility with the new custom kokoro win2019 image (#32649)#33052
veblush merged 2 commits intogrpc:v1.52.xfrom
eugeneo:release/fix-python

Conversation

@eugeneo
Copy link
Copy Markdown
Contributor

@eugeneo eugeneo commented May 9, 2023

Fix incompatibilities identified when running adhoc runs on the new custom win2019 image.
After merging this, it should be possible to switch to the new image without breaking any tests.

  • for most fixes I added a comment that explains why they're necessary.
  • the new image won't have VS2015 installed, so I'm switching the protoc artifact build to VS2017

This PR will need to be backported to older release branches to ensure the windows tests continue working on those branches as well (IMHO I haven't made any changes that would be difficult to backport and I tried to keeps the diff as small as possible to avoid issues when backporting).

After we switch to the new image (and all the windows tests are green), we can incrementally move the builds that are still using VS2017 to VS2019.

…2649)

Fix incompatibilities identified when running adhoc runs on the new
custom win2019 image.
After merging this, it should be possible to switch to the new image
without breaking any tests.

- for most fixes I added a comment that explains why they're necessary.
- the new image won't have VS2015 installed, so I'm switching the protoc
artifact build to VS2017

This PR will need to be backported to older release branches to ensure
the windows tests continue working on those branches as well (IMHO I
haven't made any changes that would be difficult to backport and I tried
to keeps the diff as small as possible to avoid issues when
backporting).

After we switch to the new image (and all the windows tests are green),
we can incrementally move the builds that are still using VS2017 to
VS2019.
@veblush veblush merged commit 14ac689 into grpc:v1.52.x May 9, 2023
@eugeneo eugeneo deleted the release/fix-python branch May 9, 2023 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants