You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
This should return a result and not remain in the 'running' state 'forever'. I waited for several minutes until I cancelled the job. This job should only take a couple of seconds.
Suggested solutions
Additional Information
This problem does not occur if I use the SamplerV2 instead of the EstimatorV2.
This does not throw a python error.
qiskit-ibm-runtime version:
0.25.0
Python version:
3.10.14
Operating system:
Windows 11 Pro, Version 23H2
The text was updated successfully, but these errors were encountered:
I ran your code snippets without any issues. Since you're running a job on real hardware there's a good chance that your job was in queue waiting to run. You can check the status of your jobs here https://quantum.ibm.com/workloads
Hi @kt474
Thank you on the update in this topic. I checked the status of my job on [https://quantum.ibm.com/workloads] and I meant the 'running' state on that website under 'Status timeline' after 'Pending' was completed. I have attached a screenshot of this job running for over 2 minutes (it started 7:10 pm and at the time of the screenshot it was 7:13 pm) with the added line of code estimator.options.default_shots=10 so that the job should take practically not time.
Just to be sure I also ran the code without that added line and again the job does not finish. (Screenshot also attached, this has the pending time of nearly 9 minutes.)
Describe the bug
Job never finishes when using EstimatorV2 with a parametrized circuit, custom gates and pulse calibrations.
Steps to reproduce
This is a simple example to reproduce this error:
Second block:
Last block:
Expected behavior
This should return a result and not remain in the 'running' state 'forever'. I waited for several minutes until I cancelled the job. This job should only take a couple of seconds.
Suggested solutions
Additional Information
This problem does not occur if I use the SamplerV2 instead of the EstimatorV2.
This does not throw a python error.
The text was updated successfully, but these errors were encountered: