It happens on Windows with MSVC 17.10 and later. Fix in #8251 is not complete, unfortunately.
Run setenvvar.bat few times in the same console and check MSVC_RUNTIME_MINOR_VERSION value after each run - first time there will be correct value '3', on the second run - '4', and so on.
The problem is in way how Windows command interpreter evaluates values of environment variables.
See https://devblogs.microsoft.com/oldnewthing/20060823-00/?p=29993, for example.
When run_all.bat is called with PDB switch, it calls setenvvar.bat twice and second run leads to a same problem as described in #8251.
It happens on Windows with MSVC 17.10 and later. Fix in #8251 is not complete, unfortunately.
Run
setenvvar.batfew times in the same console and check MSVC_RUNTIME_MINOR_VERSION value after each run - first time there will be correct value '3', on the second run - '4', and so on.The problem is in way how Windows command interpreter evaluates values of environment variables.
See https://devblogs.microsoft.com/oldnewthing/20060823-00/?p=29993, for example.
When
run_all.batis called with PDB switch, it callssetenvvar.battwice and second run leads to a same problem as described in #8251.