-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix failing Nox tests session on Windows #337
Conversation
Codecov Report
@@ Coverage Diff @@
## master #337 +/- ##
=======================================
Coverage 92.69% 92.69%
=======================================
Files 43 43
Lines 3216 3216
Branches 321 321
=======================================
Hits 2981 2981
Misses 198 198
Partials 37 37 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, its always challenging supporting Windows! Just note the comment that we might as well make the change now
noxfile.py
Outdated
@@ -95,6 +95,8 @@ def tests(session): | |||
# version didn't fix the `2to3` issue when building Python ICAT, perhaps because | |||
# Python ICAT isn't built on the downgraded version for some reason? | |||
session.run("poetry", "run", "pip", "uninstall", "-y", "setuptools") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency, you might as well remove the poetry run from the uninstall - I did this on my machine without issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, I removed it.
…-facilities/datagateway-api into fix-nox-test-session-on-windows-#307
This PR will close #307
Description
Fixes the failing
nox
tests
session on Windows.Testing Instructions
icatdb Generator Script Consistency Test
CI job fails, is this because of a deliberate change made to the script to change generated data (which isn't actually a problem) or is here an underlying issue with the changes made?fix:
,feat:
orBREAKING CHANGE:
so a release is automatically made via GitHub Actions upon merge?nox
tests
session should not failsetuptools
should be<58.0.0