Appveyor -- test against 3.12 instead of 3.11 #7592
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yarikoptic
added
the
semver-tests
|
hm, both runs "failed" but I think just timed out (since reached an hour and logs are not showing any sign of completion)? I will produce changelog entry which will trigger rerun - let's see what would happen. FWIW last run with 3.11 was under half hours edit: I have just "fixed" duecredit issue by releasing it with 3.12 support, so it might be that our mileage would improve here if underlying culprit was duecredit. |
yarikoptic
added
the
CHANGELOG-missing
github-actions
bot
removed
the
CHANGELOG-missing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related issues which might (or not) have in relation to 3.12:
and full list collected/listed in