Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Decide what `tests/runtime_smoke.py` is: pytest never collects it, it writes `tmp_smoke_test/` into the cwd, and `testing.md` misdescribes it

Abierto
  • ¿Algo no está bien?
#912 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
30/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
huggingface, python
Área
testing

Línea de trabajo

Start with tests/runtime_smoke.py, pyproject.toml (the testpaths setting that keeps pytest from collecting it), and the testing.md description. Choose one of the three recorded options (delete, move to tools/, or rename with mocked loading), since the issue does not decide it. Done means no uncollected script remains under tests/, nothing writes to tmp_smoke_test/ in the cwd, the docs match the code, and the deferral row and CHANGELOG cite F-PR29-A4-05.

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

Descripción

area: dev-tooling severity: low source: roadmap wave: 4

Deferred work · F-PR29-A4-05 · severity Low · cost ~1 h · recorded in docs/roadmap/risks-and-decisions.md:83

Summary

tests/runtime_smoke.py is the only script that runs a real one-step training (SmolLM2-135M), but its name keeps pytest from collecting it, so it never runs. It writes into ./tmp_smoke_test with the cleanup commented out, carries Turkish comments, and testing.md presents it as a dry-run fixture. Options recorded at PR #29: move it to tools/manual_smoke.py as a documented release gate, or rename it with mocked model loading and tmp_path; folding it into the nightly smoke #106 asks for is a third.

Condition or budget

None recorded (the row still names v0.6.x).

State today (re-checked 2026-10-09)

The file is unchanged since 2026-04-26; pyproject.toml sets only testpaths, so it is not collected.

Related

#106 (CR-A16-022) asks for an unmocked nightly smoke per trainer_type; it names this file but not its disposition.

Acceptance criteria

  • The file is deleted, folded into the nightly smoke, or moved to tools/ as a documented release-gate check — no uncollected script is left under tests/.
  • Nothing writes into the working directory, comments are English, and testing.md describes what exists.
  • The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).

Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.

Lenguaje dominante
Python
Estrellas
9
Forks
1
Merge medio
8 h 10 min
PR fusionados (30 d)
5

Preparar el entorno

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 HodeTech/ForgeLM

Todos los issues de HodeTech/ForgeLM

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.