Build errors: install_force has not been created.

[sandreenko]

The full error:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(231,5): error MSB8065: Custom build for item "F:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-Windows_NT-Release-x86\CMakeFiles\01d9c98fded5d1e41907661a010b2e75\INSTALL_force.rule" succeeded, but specified output "f:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-windows_nt-release-x86\cmakefiles\install_force" has not been created. This may cause incremental build to work incorrectly. [F:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-Windows_NT-Release-x86\install.vcxproj] [F:\workspace\_work\1\s\src\libraries\Native\build-native.proj]
##[error]C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(231,5): error MSB8065: (NETCORE_ENGINEERING_TELEMETRY=Build) Custom build for item "F:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-Windows_NT-Release-x86\CMakeFiles\01d9c98fded5d1e41907661a010b2e75\INSTALL_force.rule" succeeded, but specified output "f:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-windows_nt-release-x86\cmakefiles\install_force" has not been created. This may cause incremental build to work incorrectly. [F:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-Windows_NT-Release-x86\install.vcxproj]

Saw this error in a several runs today:
https://dev.azure.com/dnceng/public/_build/results?buildId=537120
https://dev.azure.com/dnceng/public/_build/results?buildId=537213

The symptoms match this old issue #32483, could cmake be downgraded on these machines?

PTAL @dotnet/runtime-infrastructure

[jaredpar]

Changed label to blocking-official-build. Generally the blocking-clean-ci is meant for issues that block the core PR / CI loop and this isn't affecting that. It is blocking our optional CI runs though. We should probably add a new label for that.

The reason for having a clean separatation of labels here is about prioritization and tracking.

[jaredpar]

Added blocking-clean-ci-optional to track this type of issue

[jaredpar]

Actually this is happening in our CI jobs right now. Consider this build https://dev.azure.com/dnceng/public/_build/results?buildId=536905

      warning Code C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(231,5): warning MSB8065: (NETCORE_ENGINEERING_TELEMETRY=Build) Custom build for item "F:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-Windows_NT-Release-x86\CMakeFiles\01d9c98fded5d1e41907661a010b2e75\INSTALL_force.rule" succeeded, but specified output "f:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-windows_nt-release-x86\cmakefiles\install_force" has not been created. This may cause incremental build to work incorrectly. [F:\workspace\_work\1\s\artifacts\obj\native\netcoreapp5.0-Windows_NT-Release-x86\install.vcxproj]

That seems to be the root of the problem here. We've let this be a warning in PR have it as an error elsewhere. @ViktorHofer @jashook why do we do this? Seems like a significant hole.

[jkoritzinsky]

@safern looks like you might have missed another hole in your recent change.

[jaredpar]

@jkoritzinsky at the moment @safern is OOF. Can you go about flipping this back to error here? This is blocking a lot of changes at the moment.

[jkoritzinsky]

We can't flip this back to error without blocking all CI. The current workaround is to mirror #32853 for all of the optional CI runs. (#32853 fixes this for the official build). I can go do that, but I want to wait for #32853 to get merged first so we can decide how we want to handle this specifically since there's some discussion about what fix we want to do.

[jaredpar]

@jkoritzinsky

We can't flip this back to error without blocking all CI.

Why can't we flip it in a PR and resolve the breaks?

[jkoritzinsky]

The errors are caused by the new version of VS causing the warning but the CMake that ships with VS not having the fix for the VS warning (pre-CMake 3.15.5). Since we have warnAsError set to true, this causes the failures. The VS preview pool has a VS that ships with a new enough CMake that this isn't a problem.

[jaredpar]

@jkoritzinsky

I find your comment confusing. Can you clarify? We own all the infra here so what pieces need to change to make this happen.

I want to make sure we have the appropriate priority here. Our official builds are 100% blocked right now. The M2's have commented that official builds must be our highest priority item here. We need to resolve this.