Run Python's slowest tests in the first 3/4 of tests when using -r
Open
Nobody has claimed this yet.
3.7 (EOL)
tests
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 30498 |
|---|---|
| Nosy | @brettcannon, @terryjreedy, @serhiy-storchaka |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2017-05-28.19:41:20.833>
labels = ['3.7', 'tests']
title = "Run Python's slowest tests in the first 3/4 of tests when using -r"
updated_at = <Date 2017-06-03.18:25:10.238>
user = 'https://github.com/brettcannon'
bugs.python.org fields:
activity = <Date 2017-06-03.18:25:10.238>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2017-05-28.19:41:20.833>
creator = 'brett.cannon'
dependencies = []
files = []
hgrepos = []
issue_num = 30498
keywords = []
message_count = 5.0
messages = ['294658', '294660', '295061', '295090', '295095']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'terry.reedy', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue30498'
versions = ['Python 3.7']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the test runner entry point that handles the -r option and reviewing the tests-related logic around ordering. Confirm how test durations are tracked or selected, then verify that the slowest tests run within the first three-quarters of the test run when -r is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100