python / python/cpython

test_copyxattr_symlinks fails

Open
#73,503 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tests
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 29317
Nosy @tiran, @thehesiod, @nitishch

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-01-18.23:33:31.895>
labels = ['tests']
title = 'test_copyxattr_symlinks fails'
updated_at = <Date 2021-12-05.23:25:12.670>
user = 'https://bugs.python.org/marktay'

bugs.python.org fields:

activity = <Date 2021-12-05.23:25:12.670>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2017-01-18.23:33:31.895>
creator = 'marktay'
dependencies = []
files = []
hgrepos = []
issue_num = 29317
keywords = []
message_count = 1.0
messages = ['285764']
nosy_count = 4.0
nosy_names = ['christian.heimes', 'thehesiod', 'marktay', 'nitishch']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue29317'
versions = ['Python 3.5', 'Python 3.6']

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.

Research direction

Start by locating and reproducing the test_copyxattr_symlinks failure in the CPython test suite, then inspect the test and its platform-specific behavior. Done means the test passes reliably on the affected systems without weakening its coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.