NVIDIA / NVIDIA/cuda-quantum

[CI] [macos] worker 'gw1' crashed while running 'build/validation/tests/kernel/test_run_kernel.py::test_simple_run_ghz_with_noise'

Open
#4,281 0 comments 0 reactions 0 assignees View on GitHub

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/actions/runs/24160627812/job/70512360514?pr=4258

=================================== FAILURES ===================================
_______________ build/validation/tests/kernel/test_run_kernel.py _______________
[gw1] darwin -- Python 3.12.10 /Users/runner/.venv/cudaq-validation/bin/python3
worker 'gw1' crashed while running 'build/validation/tests/kernel/test_run_kernel.py::test_simple_run_ghz_with_noise'
=========================== short test summary info ============================
FAILED ../../../../../../../Users/runner/work/cuda-quantum/cuda-quantum/build/validation/tests/kernel/test_run_kernel.py::test_simple_run_ghz_with_noise
============ 1 failed, 1019 passed, 125 skipped in 62.19s (0:01:02) ============
\e[01;31mPython tests failed.\e[0m
Running backend tests.
Steps to reproduce the bug

N/A

Expected behavior

N/A

Is this a regression? If it is, put the last known working version (or commit) here.

Not a regression

Environment
  • CUDA-Q version:
  • Python version:
  • C++ compiler:
  • Operating system:
Suggestions

No response

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.

Research direction

Start with build/validation/tests/kernel/test_run_kernel.py::test_simple_run_ghz_with_noise and the linked macOS Actions job to inspect the worker crash. Reproduce or isolate the failure if possible, then verify that the test completes successfully on macOS without crashing the worker.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ci-cd, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.