-
Notifications
You must be signed in to change notification settings - Fork 31
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
Empty logs after a failed import statement #1105
Comments
`'fd64febc-0c45-48cf-837b-6c121deea404' result and logs were empty for this script when the same script successfully ran on previous iteration |
@caleb-johnson can you share a version of this script so we can try to reproduce? |
I don't believe the contents of the script, or any specific issue with the source code, was causing this. It seemed like intermittently the job logs would be empty, regardless of what was contained in the code or the expected I had a hypothesis that maybe I was spamming the jupyter notebook cells too fast and ~4 API calls were being submitted simultaneously (submit, result, job_id, logs) and it was causing the logs API call to behave strangely. I'm not sure if that is a possibility, but a few times it errored in this way I did notice I had run multiple cells/API calls within less than a second |
This is the notebook script which intermittently/incorrectly returned empty logs. The contents of the source code didn't seem to play a role. Each spaced block of code represents a new cell in the notebook (in case this is some kind of jupyter bug). I would wait until status reported that it had completed successfully, but the logs would be empty even after successful completion of the job. |
Thanks @caleb-johnson , will try to break stuff shortly 😄 |
Job id 'd5234ef5-2873-44b9-a205-4fad9aab1fdc' had an import statement that wasn't available in the deployed Qiskit version (qiskit.circuit.lilbrary.UnitaryOverlap)
The problem is that for this particular job, job.logs() returned empty, instead of returning the import error. The same thing happened for several runs before this.
Job ID '0b3eeb8f-55c0-42ff-87c3-b3c285683380' properly displayed the error in the logs, but one thing I did different in this job was that I embedded print statements throughout the script. I'm not sure if that played a part, or if it randomly worked as expected in this job.
The text was updated successfully, but these errors were encountered: