load_tests chaining into discover from non-discover entry point gets top_level_dir wrong

Abierto
#66,952 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
testing-qa

Línea de trabajo

Start by reproducing load_tests chaining into discover from a non-discover entry point, then trace how top_level_dir is determined during that path. Done means discovery uses the correct top_level_dir; the issue names no files or tests, so locating the relevant unittest discovery code and regression test is part of the work.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

tests
BPO 22763
Nosy @rbtcollins, @bitdancer

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-10-30.03:13:07.277>
labels = ['tests']
title = 'load_tests chaining into discover from non-discover entry point gets top_level_dir wrong'
updated_at = <Date 2014-11-01.01:32:48.588>
user = 'https://github.com/rbtcollins'

bugs.python.org fields:

activity = <Date 2014-11-01.01:32:48.588>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2014-10-30.03:13:07.277>
creator = 'rbcollins'
dependencies = []
files = []
hgrepos = []
issue_num = 22763
keywords = []
message_count = 2.0
messages = ['230253', '230268']
nosy_count = 2.0
nosy_names = ['rbcollins', 'r.david.murray']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue22763'
versions = ['Python 3.5']

Lenguaje dominante
Python
Estrellas
77.2k
Forks
36k
Merge medio
1 d 9 h
PR fusionados (30 d)
558

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de python/cpython

Todos los issues de python/cpython

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.