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
Requested feature
We should test CLIs, MCUs, other clients in CI
Motivation
At the time of writing, it's not very easy to test anything more complicated than a standalone rust executable, this is because we rely on the TrustZone tests, which in turn rely on QEMU to execute code in an Arm environment where we know TrustZone exists. However this is a bit limited as we don't build in the same QEMU environment, requiring a copy from build environment to runtime environment.
The closest solution would be to use the Linux-process based target (#116), though there are other options such as IceCap (#149) or supporting SGX in CI.
Once we have support for native execution of an isolate target, this issue is to track the need to add the CLIs, MCUs and any other clients to CI afterwards.
The text was updated successfully, but these errors were encountered:
Requested feature
We should test CLIs, MCUs, other clients in CI
Motivation
At the time of writing, it's not very easy to test anything more complicated than a standalone rust executable, this is because we rely on the TrustZone tests, which in turn rely on QEMU to execute code in an Arm environment where we know TrustZone exists. However this is a bit limited as we don't build in the same QEMU environment, requiring a copy from build environment to runtime environment.
The closest solution would be to use the Linux-process based target (#116), though there are other options such as IceCap (#149) or supporting SGX in CI.
Once we have support for native execution of an isolate target, this issue is to track the need to add the CLIs, MCUs and any other clients to CI afterwards.
The text was updated successfully, but these errors were encountered: