Fix unit tests runner #115
Merged
Conversation
This file contains hidden or 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
alexjrk
force-pushed
the
fix/fix-unit-tests-runners
branch
from
d4f3035 to
a663c02
Compare
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The unit test runner is broken for Python 3.7 because the latest Ubuntu version (
24.04), which we are using, does not include Python 3.7.The integration test runner was also broken because it used a legacy Python base image (
3.11-slim-buster). I have updated it to use3.11-slim-bookworminstead.Until we drop support for 3.7, I have pinned the Ubuntu version to
22.04to keep the runner working.Also, updated
setup-pythonaction to the latest version