We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes this test fails for no obvious reasons. We don't see this upstream on our own runner, but it happens here sometimes:
[Enclave] (MU-RA-Server) MU-RA successful sending keys [Enclave] (MU-RA-Server) MU-RA successful, calling handle_shard_request_from_client() [Enclave] (MU-RA-Server) handle_shard_request_from_client, calling read_shard() [Enclave] (MU-RA-Server) await_shard_request_from_client, calling read_exact() [Enclave] (MU-RA-Server) handle_shard_request_from_client, await_shard_request_from_client() OK [Enclave] (MU-RA-Server) handle_shard_request_from_client, write_all() [2023-11-15T08:28:54Z ERROR enclave_runtime::tls_ra::tls_ra_server] failed to add shard vault proxy for : Other("shard not initialized") thread '<unnamed>' panicked at 'unexpected error during closedir: Os { code: 9, kind: Uncategorized, message: "Bad file descriptor" }', /opt/rust/git/checkouts/incubator-teaclave-sgx-sdk-c63c8825343e87f0/f1776a7/sgx_tstd/src/sys/fs.rs:241:9 testing tls_ra::tests::test_state_and_key_provisioning ... failed!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Sometimes this test fails for no obvious reasons. We don't see this upstream on our own runner, but it happens here sometimes:
The text was updated successfully, but these errors were encountered: