-
Notifications
You must be signed in to change notification settings - Fork 3
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
Tests running on CPU #152
Comments
Repro test case doesn't work
works
Essentially, if you force the "initialize" stage that happens in |
@mmanzoorTT @tapspatel Thank you for reporting this, IIRC @kmitrovicTT was aware of this issue and should be fixed now that transition to the new test infra is finished. @kmitrovicTT can you please verify/confirm? |
@ajakovljevicTT also mentioned this issue here: #145 |
Sorry, missed this in my emails. Yup, this should be gone now that there is no mix between the old and new infra. Upon running any test, plugin will be automatically registered due to the way singleton I'm closing this issue as obsolete, should have closed it with #136. |
Testing infrastructure is running both instances on the CPU. The desired behaviour is to run one instance on
tt
device and other on cpu to compare the outcome of both instances. It seems thatDeviceConnecter
class is not behaving as expected and is unable to registertt
plugin/device.The text was updated successfully, but these errors were encountered: