TST: add MSVC 2015 / Python 3.5 to CI #12529
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on comment suggesting we do this to reproduce the test failures reported in #12520.
Of course, what this currently does is fail other tests for reasons I don't fully understand, instead of reproducing the desired failures.
If past experience is any guide, getting the CI run to work just right for this older compiler set without pre-installed Python 3.5 on the image could be more challenging than fixing the bug itself, but may be worth it to prevent regressions, etc.
Some paths / library paths may still need adjusting given the "manual" install of Python vs. the pre-loaded cases in our newer-compiler matrix for Windows.