Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
job.cancel() returns true but job not cancelled
See original GitHub issueInformation
-
Qiskit IBMQ Provider version:
-
API URL or version:
-
Python version:
-
Operating system:
What is the current behavior?
job.cancel() can return True even if the cancel had failed.
Steps to reproduce the problem
It cannot be reproduced at will, but show up in several Travis runs (e.g. 1425 and 1414)
What is the expected behavior?
Job is cancelled if job.cancel() returns true.
Suggested solutions
The provider currently checks for error in the response data to determine if the cancel was successful. After talking to the api team, it should also be checking for 'cancelled': True in the response data.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
API rolled out a new release that had a job cancel related fix. This should be re-tested and see if we can close.
In some specific window
cancel()may still fail even withcancelled: True.