-
Notifications
You must be signed in to change notification settings - Fork 232
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
Don't create DSession in collect-only mode #232
Conversation
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.
this is a good enhancement 👍 , thanks for taking the time to make it
please add a test to prevent regression
xdist/plugin.py
Outdated
config.pluginmanager.register(session, "dsession") | ||
tr = config.pluginmanager.getplugin("terminalreporter") | ||
tr.showfspath = False | ||
if config.getoption("boxed"): |
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.
this "incorrectly" disaables the aliasing of boxed to forked,
it just doesn't show because collectonly doesnt run any tests
Re-enable parsing of the boxed option with collect-only
I've added an acceptance test and some unit tests in test_plugin. I've also re-enable the boxed option with collect-only even though it has no effect since no tests are run. |
well done will merge after pass |
flake8 strikes again ^^ |
Oops, sorry! |
don't worry, i suffer the same fate way to regular ^^ |
@@ -44,6 +44,36 @@ def test_auto_detect_cpus(testdir, monkeypatch): | |||
assert config.getoption('numprocesses') == 99 | |||
|
|||
|
|||
def test_boxed_with_collect_only(testdir): |
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.
i would consider that on unnecessary - forked/boxed got removed from xdist
Fixes #5
Thanks for submitting a PR, your contribution is really appreciated!
Here's a quick checklist that should be present in PRs:
Make sure to include reasonable tests for your change if necessary
We use towncrier for changelog management, so please add a news file into the
changelog
folder following these guidelines:Name it
$issue_id.$type
for example588.bugfix
;If you don't have an issue_id change it to the PR id after creating it
Ensure type is one of
removal
,feature
,bugfix
,vendor
,doc
ortrivial
Make sure to use full sentences with correct case and punctuation, for example: