-
Notifications
You must be signed in to change notification settings - Fork 301
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
Infrom user why rt policy could not be set, infrom if is set. #1705
Infrom user why rt policy could not be set, infrom if is set. #1705
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1705 +/- ##
==========================================
- Coverage 86.81% 86.80% -0.01%
==========================================
Files 116 116
Lines 10595 10596 +1
Branches 975 975
==========================================
Hits 9198 9198
- Misses 1047 1048 +1
Partials 350 350
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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. I guess that there is no way to check this part of the code in our github CI, or would there be a possibility to fake the RT kernel inside a container? #610
Print out information why setting of rt policy could not be set. Additionally inform if successfully set the rt policy