[CI] - re-enable unitary_compilation_diffusion_models.ipynb
Open
Nobody has claimed this yet.
stale-notified
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 455
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
- If possible, make a PR with a failing test to give us a starting point to work on!
Describe the bug
https://github.com/NVIDIA/cuda-quantum/pull/4466 disabled the jupyter notebook due to flaky issues. Investigate the actual failure and re-enable the notebook.
Steps to reproduce the bug
CI
Expected behavior
No time out
Is this a regression? If it is, put the last known working version (or commit) here.
Not a regression
Environment
CI
Suggestions
No response
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 with unitary_compilation_diffusion_models.ipynb and the CI changes in pull request #4466. Reproduce the notebook's CI failure, identify the flaky or timing issue, and re-enable the notebook once the CI run completes without timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100