-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timing bug (RuntimeError) in running analysis with block_for_results() #1185
Comments
The reason for this behavior (which is not a bug) is that the line This raises the question of whether we should use the default |
@gadial Thank you for letting me know the spec. I should have read the API doc carefully.
or
|
The rerun analysis how-to has been updated with the correct syntax for running the analysis so that the current experiment data object is overwritten instead of creating a new one. Closes #1185. --------- Co-authored-by: Toshinari Itoko <[email protected]>
The rerun analysis how-to has been updated with the correct syntax for running the analysis so that the current experiment data object is overwritten instead of creating a new one. Closes #1185. --------- Co-authored-by: Toshinari Itoko <[email protected]> (cherry picked from commit 8cc20df)
The rerun analysis how-to has been updated with the correct syntax for running the analysis so that the current experiment data object is overwritten instead of creating a new one. Closes qiskit-community#1185. --------- Co-authored-by: Toshinari Itoko <[email protected]>
Informations
What is the current behavior?
Running an analysis (e.g. Parallel T1) with
block_for_results()
occasionally fails with aRuntimeError: cannot schedule new futures after interpreter shutdown
. It may suggestblock_for_results()
does not actually wait for the completion of results.Steps to reproduce the problem
Running the code below via command line.
Try rerun the "load and rerun analysis" part with your experiment_id if no error happens in your env.
What is the expected behavior?
block_for_results
should wait for the completion of analysis.The text was updated successfully, but these errors were encountered: