Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#912 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
huggingface, python
Domain
testing

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
9
Forks
1
Avg merge
8h 10m
Merged PRs (30d)
5

Getting set up

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

All issues in HodeTech/ForgeLM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.