tests failing with -uall and http_proxy and https_proxy set

Open
#66,566 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the attached python3.4-net-tests log and the original BPO issue 22371. Reproduce the failures with -uall while http_proxy and https_proxy are set, then trace the failing network tests. Done means the affected test suite passes under that environment or the failure is clearly isolated and documented.

Written by the indexing model from the issue text.

Description

tests
BPO 22371
Nosy @doko42
Files
  • python3.4-net-tests: test log
    		•

    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-09-09.18:00:20.733>
labels = []
title = 'tests failing with -uall and http_proxy and https_proxy set'
updated_at = <Date 2014-09-09.18:04:18.649>
user = 'https://github.com/doko42'

    bugs.python.org fields:

    activity = <Date 2014-09-09.18:04:18.649>
actor = 'doko'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2014-09-09.18:00:20.733>
creator = 'doko'
dependencies = []
files = ['36584']
hgrepos = []
issue_num = 22371
keywords = []
message_count = 2.0
messages = ['226650', '226652']
nosy_count = 1.0
nosy_names = ['doko']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue22371'
versions = []

    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.