-
Notifications
You must be signed in to change notification settings - Fork 13
COCOS-456 Remove SEV support from repo #472
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
COCOS-456 Remove SEV support from repo #472
Conversation
4297033 to
9bf39e8
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #472 +/- ##
==========================================
- Coverage 47.47% 47.46% -0.01%
==========================================
Files 68 68
Lines 6359 6341 -18
==========================================
- Hits 3019 3010 -9
+ Misses 3025 3015 -10
- Partials 315 316 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
SammyOina
left a comment
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.
also look into more of the code base for specific sev conditions which are no longer needed, update readme docs as well . https://github.com/dorcaslitunya/cocos/blob/dorcaslitunya/cocos-456/remove-sev/manager/README.md https://github.com/dorcaslitunya/cocos/blob/9bf39e8e539e81c661ea6cfff831294b61453ac7/manager/qemu/vm.go#L67
these are just some examples, there should be more changes needed
c95bab3 to
b942804
Compare
3f75f91 to
e68a881
Compare
e68a881 to
124f97e
Compare
danko-miladinovic
left a comment
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.
LGTM
2def763 to
c7a3ea5
Compare
c7a3ea5 to
a5b5336
Compare
What type of PR is this?
This is a feature as it removes SEV support from cocos
What does this do?
Remove SEV support in cocos
Which issue(s) does this PR fix/relate to?
#456
Have you included tests for your changes?
No tests needed as it is removing a feature
Did you document any new/modified feature?
No, but documentation will be updated in a separate PR
Notes