GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — gh-119727: Add --single-process option to regrtest by vstinner · Pull Request #119728 · python/cpython Conversation
|
| group.add_argument('-j', '--multiprocess', metavar='PROCESSES', | ||
| dest='use_mp', type=int, | ||
| help='run PROCESSES processes at once') | ||
| group.add_argument('--sequentially', action='store_true', |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
You can also implement it as action='store_const', dest='use_mp', const=None.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| NEED_TTY = set(''' | ||
| test_ioctl | ||
| '''.split()) | ||
| NEED_TTY = { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Not related.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's a follow-up of a previous PR. I didn't want to write a dedicated PR for that.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@Yhg1s @hugovk: Since the release process requires to run tests sequentially, do you have a preference for the option name?
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
My first thought is to use something like This is similar to pytest-xdist ( |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Currently, -j1 runs tests sequentially but spawn a new process for each test file: see #119727 (comment). I'm open to consider changing this behavior. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Do you think anyone will realistically want to run sequentially and spawn a new process for each? My guess is not. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I'm a little bit worried that some projects currently run tests with According to the discussion, the least bad choice is |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Then I'd include a hyphen for readability/accessibility: We have a mixture of options with and without hyphens, so consistency isn't a problem :) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I updated the PR to use |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
It does not really matter. It was just a tiny nitpick from my side. Use the name that you like if you are sure that it will not create problems in future. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
…aZM.rst Co-authored-by: Hugo van Kemenade <[email protected]>
|
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @vstinner, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I'll submit a backport of this because it would be useful for the iOS and Android buildbots – #122992 (comment). |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
(cherry picked from commit 4e8aa32)
|
GH-123010 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @vstinner, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…onGH-119728) (cherry picked from commit 4e8aa32) Co-authored-by: Victor Stinner <[email protected]>
|
GH-130359 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…#130359) Co-authored-by: Victor Stinner <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.