Run `make smoke` on Apple Silicon or ROCm and record results in `docs/hardware-matrix.md`

Open
  • Is something wrong?
#14 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python, pytorch
Domain
documentation, machine-learning

Research direction

Read the README’s “Try it” instructions and inspect src/ofl/smoke/ to see what each smoke step checks. Run make setup && make doctor && make smoke on an Apple Silicon Mac or AMD GPU machine, then record the hardware, software versions, results, errors, date, and reporter handle in docs/hardware-matrix.md. Link the matrix from docs/ARCHITECTURE.md §1; done means the matrix contains a real row and make check and make test pass.

Written by the indexing model from the issue text.

Description

agent-authored area/docs good first issue help wanted layer/1-hardware type/docs

Context

Nothing has been tested on Apple Silicon or ROCm (ARCHITECTURE §1). Before Hello, swarm we need to know which steps work where.

Task

Run make setup && make doctor && make smoke on a Mac (M-series) or an AMD GPU machine. Create docs/hardware-matrix.md with a table (hardware, OS, Python, torch, each smoke step pass/fail, notes, date, reporter handle) and add your row. Failures are results: record the error.

Definition of done

  • docs/hardware-matrix.md exists with the table and at least one real row
  • Exact error output for any failing step is in the PR description
  • Linked from docs/ARCHITECTURE.md §1
  • make check and make test pass
  • Commits signed off (git commit -s)

Pointers

  • README: Try it, src/ofl/smoke/
  • One row per machine; more contributors can add rows later
  • Ask in Discord #compute-nodes, or comment here. Comment "I'll take this" to be assigned. A draft PR after an hour of work is welcome.

Skills: Any hardware (a Mac or AMD GPU)

Agent: omp / claude-opus-5-5 (issue drafted by an agent; a maintainer reviews the PR)

Dominant language
Python
Stars
1
Forks
2
Avg merge
2h 4m
Merged PRs (30d)
23

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 OpenFrontierLabs/openfrontier

All issues in OpenFrontierLabs/openfrontier

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.