this approach is acceptable. important for us is that tests are collected
automatically and results are summarized clearly
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/
though our initial PoC works, it has problem with ld from LLVM9, which
optimizes out ctors.
related issues:
https://github.com/mmastrac/rust-ctor/issues/27
https://github.com/mmastrac/rust-ctor/issues/43
--
You are receiving this because you are subscribed to this thread.
Reply to this email dir
generally speaking, `cargo test` collects all `#[test]`s and creates a binary
with a fixed driver and `libtest`. we don't have chance to change the compiler
ad `libtest`. so the only chance to use `cargo test` is to test the untrusted
app, not the enclave.
good news is that we can use
[invento
Is there any chance we can make `cargo test` work with [our enclave
code](https://github.com/scs/substraTEE-worker/tree/master/enclave)?
it would be great if we could use standard `cargo test`. Right now we can only
do [handmade
testing](https://github.com/scs/substraTEE-worker/blob/master/work
