Fortnightly notebook test failed
Open
Nobody has claimed this yet.
needs triage 🤔
- Dominant language
- Jupyter Notebook
- Stars
- 106
- Forks
- 223
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 72
Description
Today's scheduled test of notebooks that submit jobs failed.
Please check the logs.
[!NOTE]
This issue was created by a GitHub action.
Contributor guide
No contributing guide indexed for this repository
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 with the linked GitHub Actions run logs to identify why the scheduled notebook job failed. Inspect the notebook test that submits jobs and reproduce the failure if possible. Done means the scheduled test completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, jupyter-notebook
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100