Skip to content

Conversation

@zware
Copy link
Member

@zware zware commented Sep 4, 2018

We're currently having caching issues between the two images, and VS2017 builds are tested by VSTS.  Removing that one here will significantly decrease the time that AppVeyor builds take on this branch.
@zware zware changed the title [DO NOT MERGE] Test AppVeyor with only VS2017 [3.6] Build with only VS2015 on AppVeyor Sep 5, 2018
@zware zware changed the title [3.6] Build with only VS2015 on AppVeyor [3.6] bpo-34575: Build with only VS2015 on AppVeyor Sep 5, 2018
@vstinner
Copy link
Member

vstinner commented Sep 5, 2018

"bedevere/issue-number — No issue # in title or "skip issue" label found" stupid bot

Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

According to @zware there is a VS2017 buildbot, so I don't think that it matters to check VS2017 as pre-commit. This change should make AppVeyor twice faster on 3.6 which is a good thing, since AppVeyor is currently the slowest pre-commit CI on PRs.

@zware zware changed the title [3.6] bpo-34575: Build with only VS2015 on AppVeyor bpo-34575: [3.6] Build with only VS2015 on AppVeyor Sep 5, 2018
@zware zware changed the title bpo-34575: [3.6] Build with only VS2015 on AppVeyor [3.6] bpo-34575: Build with only VS2015 on AppVeyor Sep 5, 2018
@zware zware merged commit 635461f into python:3.6 Sep 5, 2018
@zware zware deleted the appveyor-test branch September 5, 2018 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants