tracing and tests that raise an exception in a SIGALRM handler

Open
#64,800 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems, testing-qa

Research direction

Start by reading the attached signal_test.py and comparing the no_tracing.diff, tracing_signals.patch, and tracing_signals_2.patch files. Run the relevant current CPython signal and tracing tests, then determine whether the SIGALRM exception behavior is still reproducible. Done requires a confirmed regression test and a reviewed fix for the reported interaction.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 20601
Nosy @vstinner, @xdegaye
Files
  • no_tracing.diff
  • tracing_signals.patch
  • signal_test.py
  • tracing_signals_2.patch
    		•

    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 2014-02-11.17:34:36.273>
labels = ['type-bug', 'library']
title = 'tracing and tests that raise an exception in a SIGALRM handler'
updated_at = <Date 2014-02-14.22:59:26.845>
user = 'https://github.com/xdegaye'

    bugs.python.org fields:

    activity = <Date 2014-02-14.22:59:26.845>
actor = 'xdegaye'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-02-11.17:34:36.273>
creator = 'xdegaye'
dependencies = []
files = ['34046', '34069', '34070', '34082']
hgrepos = []
issue_num = 20601
keywords = ['patch']
message_count = 6.0
messages = ['210984', '211099', '211100', '211159', '211227', '211247']
nosy_count = 2.0
nosy_names = ['vstinner', 'xdegaye']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20601'
versions = ['Python 3.4']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.