test_lzma: Multiple test failures when liblzma is built without complete codec set
Open
Nobody has claimed this yet.
3.8 (EOL)
tests
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34883 |
|---|---|
| Nosy | @mgorny, @tirkarthi |
| Files |
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 2018-10-03.10:32:44.087>
labels = ['3.8', 'type-feature', 'tests']
title = 'test_lzma: Multiple test failures when liblzma is built without complete codec set'
updated_at = <Date 2018-10-04.06:36:59.663>
user = 'https://github.com/mgorny'
bugs.python.org fields:
activity = <Date 2018-10-04.06:36:59.663>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2018-10-03.10:32:44.087>
creator = 'mgorny'
dependencies = []
files = ['47845']
hgrepos = []
issue_num = 34883
keywords = []
message_count = 1.0
messages = ['326960']
nosy_count = 2.0
nosy_names = ['mgorny', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue34883'
versions = ['Python 3.8']
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 with the test_lzma tests and the attached lzma-test.txt verbose output to identify which failures depend on missing liblzma codecs. Confirm the expected behavior for a build without the complete codec set, then run the affected tests to verify that the failures are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100