-
Notifications
You must be signed in to change notification settings - Fork 51
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
Test Jobs for V4L2 Compliance (New) #1653
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1653 +/- ##
==========================================
+ Coverage 48.96% 49.00% +0.04%
==========================================
Files 371 373 +2
Lines 40296 40332 +36
Branches 6808 6816 +8
==========================================
+ Hits 19730 19764 +34
- Misses 19846 19847 +1
- Partials 720 721 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
||
def main(): | ||
udev_out = sp.check_output( | ||
"udev_resource.py -f CAPTURE", universal_newlines=True, shell=True |
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'm not really sure if this is the correct way to access udev outputs inside a resource job since it uses shell=True
. What would be the better way to do this? 🤔
Description
This PR implements test jobs utilizing the v4l2 compliance parser. Each camera will get a job for each ioctl request, so the total number of jobs would be (n_cameras * n_ioctl_tests).
Resolved issues
Documentation
As of right now each camera will run v4l2-compliance once for every ioctl request. To test more ioctls in 1 run, pass in more ioctl names in --ioctl.
Tests
Unit tests
Test plan tested on 18, 20 VM with camera pass through, 22&24 DUTs with USB cameras.