pymc-devs / pymc-devs/pymc-examples
GitHub Action to run through notebooks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 398
- Forks
- 325
- Avg merge
- 9d 15m
- Merged PRs (30d)
- 1
Description
This is not meant to fix or update the notebooks but to get a pulse on which notebooks are no longer working. Just a smoke test
I suspect that many are outdated so I can also have the output the failure logs populate a (pinned) issue(s).
Would it make sense to keep try to run all the notebooks with the latest PyMC version? Which environment would be used here?
Any thoughts here?
Reference:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced pymc-marketing scripts/run_notebooks/runner.py and then inspect how pymc-examples currently runs notebooks. Define the environment and smoke-test scope before implementing a GitHub Action; done should include results for the notebooks and a clear way to collect failure logs in pinned issue(s).
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, jupyter-notebook, python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100