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
Currently, the caldera tests are true e2e tests since they test if the policy applied to security engine is actually doing what is intended.
We can use put this testing functionality into the current e2e tests
The text was updated successfully, but these errors were encountered:
For the coco-workload e2e test, we need KVM on the runner.
This post (https://github.blog/changelog/2023-02-23-hardware-accelerated-android-virtualization-on-actions-windows-and-linux-larger-hosted-runners/) mentions that kvm is available on large runners.
From (https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners) "if you are on the GitHub Team or GitHub Enterprise Cloud plan, you can provision a runner with more cores, or a runner that's powered by a GPU or ARM processor. These machines are referred to as "larger runner." "
The SE-RAN is neither an GitHub paid team nor a GitHub Enterprise
Sorry, something went wrong.
@VedRatan Can you link the draft PR?
Blocked as an epf runner is yet to be in place.
VedRatan
Successfully merging a pull request may close this issue.
Currently, the caldera tests are true e2e tests since they test if the policy applied to security engine is actually doing what is intended.
We can use put this testing functionality into the current e2e tests
The text was updated successfully, but these errors were encountered: