Yun Peng

The binary runs fine on the same VM image where it was built: ``` C:\Users\pcloudy\workdir>set USE_BAZEL_VERSION=7.2.0rc3 C:\Users\pcloudy\workdir>bazel 2024/06/06 09:04:06 Downloading https://releases.bazel.build/7.2.0/rc3/bazel-7.2.0rc3-windows-x86_64.exe... Downloading: 63 MB out of 63 MB (100%) Extracting...

I can confirm building with MSVC 2022 14.40.33807 causes this problem, but not when I switch to MSVC 2019.

I still haven't figured out a fix, but I can revert the Windows VM image first. However, this would revert https://github.com/bazelbuild/continuous-integration/issues/1962 /cc @ahumesky @tomrenn

I've rebuilt Bazel binaries at HEAD, and hopefully that solves the issue. @keertk We need to rerun the release pipeline for rc3, too.

OK, rc3 release have been refreshed, also fixed last_green. I'll trigger builds to fix commits on master and release-7.2.0 retrospectively.

@benjaminp 8.0.0-pre.20240530.1 should be fixed now, can you verify?

I see, I only refreshed [3e2aec2fdefea213cde0c0fc41eb40221995d1ca](https://github.com/bazelbuild/bazel/commit/3e2aec2fdefea213cde0c0fc41eb40221995d1ca). Now reran the release pipeline, should be fixed now.

@Bencodes @restingbull I can see you are the two active maintainer of rules_kotlin, how do you feel about transferring this to bazel-contrib?

ping!

ping, to keep it active