-
Notifications
You must be signed in to change notification settings - Fork 67
Add the test script to trigger and capture cpuidle state (New) #2039
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
base: main
Are you sure you want to change the base?
Conversation
535cee4
to
747e656
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2039 +/- ##
==========================================
+ Coverage 51.13% 52.37% +1.24%
==========================================
Files 386 392 +6
Lines 41603 42210 +607
Branches 7730 7826 +96
==========================================
+ Hits 21272 22108 +836
+ Misses 19569 19324 -245
- Partials 762 778 +16
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
342b28c
to
4e8943d
Compare
4e8943d
to
fae7e25
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.
I've tried the script on two of ARM devices. And seems it catch one of device didn't support cpuidle.
[INFO] Starting CPU idle state test
[INFO] This test checks if all processors have the same number of idle states and if idle state transitions happen during alternating load patterns
[INFO] Found 2 CPUs in system
[ERROR] ERROR: No CPUs with cpuidle support found
I think this test is valuable. But what the reason not implement the test job for it?
…ity and seperate the get affinity from the set function
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
Description
Resolved issues
Miss coverage of the CPU idle.
Documentation
Tests
ARM w/o CPUidle driver (this is a true issue):
ARM w/ CPUidle driver (some state can't entry during the trigger idle state testing but the usage of state w/ existing usage so mark as pass )