Stage-DotNet pipeline coherency check not detecting multiple emsdks
Recently, we had a run of the Stage-DotNet pipeline that didn't have it's incoherency detected. The validate manifest job finished without detecting two different emsdks. Later, the windows-signing failed because of this. Searching for emsdk in the logs there shows that there are two different BAR IDs: 145179 and 145171
Stage-DotNet only checks that there is only 1 runtime, 1 windowsdesktop, and 1 aspnetcore. No other aspects of coherency are checked today. I'm not sure why signing would be failing due to incoherency. @mmitche
I am going to close this as this is currently working as intended. If we ultimately want to have better coherency checking, we can discuss it, but I believe the VMR will eventually fix it itself.