build failure when enabling dtrace on FreeBSD
Open
Nobody has claimed this yet.
3.10
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
build
OS-freebsd
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29077 |
|---|---|
| Nosy | @cburroughs, @ambv, @zware, @koobs, @swills, @0mp |
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 2016-12-26.19:19:02.376>
labels = ['3.8', 'build', '3.7', '3.9', '3.10']
title = 'build failure when enabling dtrace on FreeBSD'
updated_at = <Date 2021-08-10.09:36:19.945>
user = 'https://github.com/swills'
bugs.python.org fields:
activity = <Date 2021-08-10.09:36:19.945>
actor = '0mp'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2016-12-26.19:19:02.376>
creator = 'swills'
dependencies = []
files = []
hgrepos = []
issue_num = 29077
keywords = []
message_count = 4.0
messages = ['284038', '284209', '295239', '399309']
nosy_count = 6.0
nosy_names = ['cburroughs', 'lukasz.langa', 'zach.ware', 'koobs', 'swills', '0mp']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue29077'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10']
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
The payload names no source files, tests, or entry points. Start with the linked bugs.python.org issue and reproduce the CPython build on FreeBSD with DTrace enabled; done means the build completes successfully in that configuration and the failure is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100