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
The assertion passes. The same as what would happen if the RuntimeError was not raised because the exception raised after the variable was modified.
Actual (undesired) Behavior
The assertion fails. Because of the RuntimeError, the kernel exits with a "pending" exception. I expect that is the cause. The logs show that attribute synchronization (from the kernel to the host) is not performed. Hence, attr_sync_var is still 0. Exception propagation still works fine.
This behavior is at least seen in ARTIQ 6 and 7. I have not tested 8. If there is agreement that this behavior is incorrect then I would like backporting of this fix to be considered for versions down to ARTIQ 6 if possible but at least 7 (current old stable).
Your System (omit irrelevant parts)
Operating System: Ubuntu
ARTIQ version: 7.8211
The text was updated successfully, but these errors were encountered:
Bug Report
One-Line Summary
No attribute syncing when kernel exits with an exception.
Issue Details
Steps to Reproduce
See the following example code:
Expected Behavior
The assertion passes. The same as what would happen if the
RuntimeError
was not raised because the exception raised after the variable was modified.Actual (undesired) Behavior
The assertion fails. Because of the
RuntimeError
, the kernel exits with a "pending" exception. I expect that is the cause. The logs show that attribute synchronization (from the kernel to the host) is not performed. Hence,attr_sync_var
is still 0. Exception propagation still works fine.This behavior is at least seen in ARTIQ 6 and 7. I have not tested 8. If there is agreement that this behavior is incorrect then I would like backporting of this fix to be considered for versions down to ARTIQ 6 if possible but at least 7 (current old stable).
Your System (omit irrelevant parts)
The text was updated successfully, but these errors were encountered: