BUILD: run CI with an older windows toolchain like in wheel building #21361
Conversation
b2b06a8 to
a46e679
Compare
a46e679 to
615d6ce
Compare
|
Closing. I couldn't get the BatchScript task to actually modify the environment. I think anyway #21360 is a better fix for the issue. |
| - powershell: | | ||
| ls openblas | ||
| echo What PATH and other environment variables? | ||
| echo PATH $Env:PATH |
There was a probl 8000 em hiding this comment.
For those trying to follow what happened, the PATH printed here in CI is not being modified by the previous BatchScript step, so the older 141 toolset is not used. You can see that the PATH printed at the end of tools/set_vs_toolchain.cmd is not the same as the one printed here.
|
@charris, @matthew-brett can we move the conversation around a CI run with vs 141 here from #21346? I tried copying exactly the step used in MacPython/numpy-wheels, it didn't work. I printed out the PATH at the end of the step, and the PATH at the beginning of the next one, they are different. The
I don't see such a call in the code in the step in azure/windows.yml from MacPython/numpy-wheels |
Sidenote: it's suboptimal to do this in a closed issue/PR, because it gets hidden from much more by github, and is therefore easier to overlook. How about reopening (or moving to a different issue)? |
issue #21346: