Update CI #27
Merged
Update CI #27
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
`actions/setup-python` / `actions/python-versions` dropped Python 2.7 See: actions/setup-python#672
There are two unrelated (?) issues that we should fix: * Adopt the rolling release scheme. See: luarocks#25 * Fix Windows build: `syntax error near unexpected token`
* Add 3.12 * Remove versions that we don't test (3.0-3.5
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #27 +/- ##
==========================================
- Coverage 79.87% 79.78% -0.09%
==========================================
Files 1 1
Lines 1123 1123
==========================================
- Hits 897 896 -1
- Misses 226 227 +1 ☔ View full report in Codecov by Sentry. |
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.
Once again, GitHub Actions had some surprises.
There are two almost not related to each other issues affecting the same test, I had to mark it as an expected failure to start to unravel this knot of issues.