Make 3.6 Python builds run on Ubuntu 20.04 #115
Merged
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
Codecov Report
@@ Coverage Diff @@
## master #115 +/- ##
=======================================
Coverage 89.88% 89.88%
=======================================
Files 2 2
Lines 178 178
Branches 26 26
=======================================
Hits 160 160
Misses 9 9
Partials 9 9 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
I'm overthinking this too much...
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.
I guess our workers transition to Ubuntu 22.04, which don't have Python 3.6 on them. (see actions/setup-python#355, actions/setup-python#544)
Since we need to support Python 3.6 because of Django 3.2, I propose running 3.6 tests on the older machine.