-
Notifications
You must be signed in to change notification settings - Fork 0
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
Keystone: Run Enclave functionality #271
base: main
Are you sure you want to change the base?
Conversation
75c6a76
to
3c73e64
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks good to me :)
It seems there is a timeout issue with the CI with one of the keystone test, do you have the same issue locally?
3c73e64
to
1100e80
Compare
Same issue it seems, the tests do not terminate:
The cancelation is the CI timeout. In the test payload are you exiting properly? What is happening when you run the tests in local? |
When I run the test in local, it terminates successfully, but on the CI, it seems to get stuck when jumping into the enclave. Do you have an idea of what might be the problem? |
Hmmm in general the QEMU features might be different, which version are you using? The CI is using 6.2.0 if that didn't change recently. |
I am using version 7.2.13 and I am not passing any special flags, I will try downgrading my QEMU version to see if I can replicate the bug locally Edit: The QEMU version seems to cause the issue :) |
I see, can you check with GDB where the system is stuck? Is it inside of Miralis or somewhere else? And if in Miralis, do you know where? We didn't have the issue before, so something must have changed ^^ |
No description provided.