Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Upgrade to Visual Studio 2022 in appveyor.yml#30239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Something else is wrong here. AppVeyor uses our condaenvironment.yml
, which as of#28352 includes compilers from conda-forge.
Looking at the diff between logs, conda-forge updatedc-compiler
/cxx-compiler
from 1.9.0 to 1.10.0, andvs2019_win-64
tovs2022_win-64
. Fromhttps://www.appveyor.com/docs/windows-images-software/ MSVC 2022 is in the "Visual Studio 2022" image, so we either need to pin the compilers from conda-forge, or update to that instead of our current "Visual Studio 2019".
Since we don't use these builds for wheels or anything user-facing like that, I think we should do the latter.
2899656
intomatplotlib:mainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Let's see if this resolves the build error
Previous description:
Call vcvars batch file in appveyor.yml
As perhttps://www.appveyor.com/docs/lang/cpp/
Recent Appveyor builds including#30232 and#30236 are failing with
log lines for
pip install -v --no-build-isolation --editable .[dev]
This build at least gets past that command.