Model training scripts dump generated artifacts directly into the repo root

Open
#5,672 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by inspecting the model-training scripts under scripts/ and the generated artifact names listed in the issue. Trace which entry points write into the repository root, then determine a project-consistent output location and verify training no longer places generated files there.

Written by the indexing model from the issue text.

Description

Problem

The repo root accumulates a large number of generated artifacts — mostly from model training — that are correctly .gitignore'd but still physically clutter the directory, making the project structure hard to navigate in file explorers, ls, and IDEs. The exact number depends on how many models have been trained locally during experimentation.

For example, after training several models, the root can contain ~59 items on disk while only ~31 are tracked source files — the rest are generated artifacts. Actual project files get buried among generated directories:

$ ls
CITATION.cff              fenixcomponentmodel/       regressormodel_data_X.zst.etag
CODE_OF_CONDUCT.md        functions/                 regressormodel_data_y
CONTRIBUTING.md           http_service/              regressormodel_data_y.zst
LICENSE                   indexdir/                  regressormodel_data_y.zst.etag
MANIFEST.in               infra/                     releasenotemodel/
README.md                 mcp/                       requirements.txt
VERSION                   metrics.json               scripts/
__pycache__/              node_modules/              setup.py
annotateignoremodel/      notebooks/                 spambugmodel/
backoutmodel/             patches/                   stepstoreproducemodel/
bugbug/                   pyproject.toml             test-requirements.txt
bugbug.egg-info/          regressionmodel.zst        testfailuremodel
bugtypemodel/             regressormodel.zst         testgroupselectmodel/
cache/                    regressormodel.zst.etag    testlabelselectmodel/
componentmodel/           regressormodel_data_X      tests/
crashcomponentmodel/      regressormodel_data_X.zst  ui/
data/                     regressormodel_data_X.zst… upliftmodel/
...
Dominant language
Python
Stars
570
Forks
351
Avg merge
2d 13h
Merged PRs (30d)
65

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 mozilla/bugbug

All issues in mozilla/bugbug

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.