-
Notifications
You must be signed in to change notification settings - Fork 17
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
QuantinuumJob response is sometimes JobStatus #29
base: master
Are you sure you want to change the base?
QuantinuumJob response is sometimes JobStatus #29
Conversation
…cation per stack trace in issue ticket
Just want to mention that this PR is a continuation of the recent fix from #28. I've tested this on my end and would find this being merged in fyi @1ucian0 / @mtreinish |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks fine. But besides the lint job failure that needs to be fixed I just had one minor inline comment.
Just following up on this PR. It looks like @WrathfulSpatula made the requested change asked by @mtreinish . Are there any other outstanding issues you think would be worth addressing, or is this okay to be merged into Thanks again! |
@1ucian0 @chris-theroux @mtreinish Any chance this can be merged into |
I don't have permissions to merge. Pinging @mtreinish |
Summary
(Closes #27)
Over at https://github.com/SRI-International/QC-App-Oriented-Benchmarks, we're trying to use this provider to benchmark Quantinuum devices. However, adding the provider to that repository, it always raises an exception due to an unhandled case in the method
status()
, where one or more items inself._experiment_results
is aJobStatus
instance.Following your logic in the same region of code, we extract the maximum information we can for the
experiment_result
, then we add the header and append to the results list otherwise exactly according to how it was already done.This fixes our issue in the benchmarks repository, allowing us to get the results we expect.
Details and comments
For coverage: I can see that the original code leads to an exception and stack trace in https://github.com/SRI-International/QC-App-Oriented-Benchmarks, while the code is this branch works. I'm not sure how to encapsulate this in a unit test, but, apparently, the original code coverage didn't cover this logical case, of a
JobStatus
response.