GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add `--single-process` option to regrtest to always run tests sequentially (ignore `-jN` option) · Issue #119727 · python/cpython

Add --single-process option to regrtest to always run tests sequentially (ignore -jN option) #119727

New issue
Copy link
New issue
Copy link
Closed
Closed
Add --single-process option to regrtest to always run tests sequentially (ignore -jN option)#119727
Copy link
Labels
testsTests in the Lib/test dirTests in the Lib/test dirtype-featureA feature request or enhancementA feature request or enhancement

Description

@vstinner
vstinner
opened on May 29, 2024
Issue body actions

The Python release process runs tests sequentially. It catchs some issues which are ignored silently when running tests in parallel.

I propose adding --sequentially option to regrtest to always run tests sequentially. It can be used to ignore any -jN option and also to re-run failed tests sequentially.

Linked PRs

  • gh-119727: Add --single-process option to regrtest #119728
  • gh-119727: Run tests in parallel by default #120456
  • [3.13] gh-119727: Add --single-process option to regrtest (#119728) #123010
  • [3.12] gh-119727: Add --single-process option to regrtest (GH-119728) #130359
Reacted by Kirill Podoprigora and Aidan

Activity

  1. vstinner
    added 2 commits that reference this issue on May 29, 2024

    pythongh-119727: Add --sequentially option to regrtest

    d387ad7

    pythongh-119727: Add --sequentially option to regrtest

    ef0522a
  2. vstinner commented on May 29, 2024

    @vstinner
    vstinner
    on May 29, 2024
    MemberAuthor
    More actions

    My motivation for this change is also a desire to change the regrtest default to -j0: run tests in parallel using the number of CPU.

  3. Eclips4
    added
    testsTests in the Lib/test dirTests in the Lib/test dir
    type-featureA feature request or enhancementA feature request or enhancement
    on May 29, 2024
  4. serhiy-storchaka commented on May 29, 2024

    @serhiy-storchaka
    serhiy-storchaka
    on May 29, 2024
    Member
    More actions

    This is an opposite of --multiprocess. Why not call it --singleprocess?

    You can run tests with -j1, it will be sequentially, but in different processes.

  5. vstinner commented on May 30, 2024

    @vstinner
    vstinner
    on May 30, 2024
    MemberAuthor
    More actions

    IMO "sequentially" is the right name. --multiprocess means in fact "running tests in parallel". Using multipe processes is just an implementation details. It could be threads or something else. The opposite of parallel is sequential. IMO it's too late to rename the --multiprocess option.

    Note: there is already a --single option. --singleprocess sounds too close.

  6. serhiy-storchaka commented on May 30, 2024

    @serhiy-storchaka
    serhiy-storchaka
    on May 30, 2024
    Member
    More actions

    I will not insist.

    The --multiprocess option has two effects: it runs the tests in parallel and runs every test is a separate process. It could be possible to run the tests in parallel using the process pull, but this is not how it is implemented now, and I do not think there is a benefit to implement such option. Currently there are three options:

    • Run the tests sequentially in the same (main) process. By default.
    • Run the tests sequentially in separate processes. -j1.
    • Run the tests in parallel in separate processes. -jN.
  7. vstinner
    added a commit that references this issue on Jun 3, 2024

    gh-119727: Add --single-process option to regrtest (#119728)

    4e8aa32
  8. hugovk
    changed the title [-]Add `--sequentially` option to regrtest to always run tests sequentially (ignore `-jN` option)[/-] [+]Add `--single-process` option to regrtest to always run tests sequentially (ignore `-jN` option)[/+] on Jun 3, 2024
  9. mliezun
    added a commit that references this issue on Jun 3, 2024

    pythongh-119727: Add --single-process option to regrtest (python#119728)

    035ef28
  10. barneygale
    added a commit that references this issue on Jun 5, 2024

    pythongh-119727: Add --single-process option to regrtest (python#119728)

    713d900
  11. vstinner
    added 3 commits that reference this issue on Jun 13, 2024

    pythongh-119727: Run tests in parallel by default

    6b1d321

    pythongh-119727: Run tests in parallel by default

    ddb22a6

    pythongh-119727: Run tests in parallel by default

    5517f14
  12. vstinner
    closed this as completedon Jun 13, 2024
  13. vstinner commented on Jun 13, 2024

    @vstinner
    vstinner
    on Jun 13, 2024
    MemberAuthor
    More actions

    Implemented by change 4e8aa32.

  14. estyxx
    added a commit that references this issue on Jul 17, 2024

    pythongh-119727: Add --single-process option to regrtest (python#119728)

    7dd93f0
  15. mhsmith
    added a commit that references this issue on Aug 14, 2024

    pythongh-119727: Add --single-process option to regrtest (python#119728)

    4185f2b
  16. vstinner
    added a commit that references this issue on Aug 26, 2024

    [3.13] gh-119727: Add --single-process option to regrtest (#119728) (#…

    350313e
  17. hugovk
    added 2 commits that reference this issue on Feb 20, 2025

    [3.12] pythongh-119727: Add --single-process option to regrtest (pyth…

    ccb4ead

    [3.12] gh-119727: Add --single-process option to regrtest (GH-119728) (…

    ecfca20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    testsTests in the Lib/test dirTests in the Lib/test dirtype-featureA feature request or enhancementA feature request or enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.