Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?
Test Jobs for V4L2 Compliance (New) #1653
Changes from 16 commits
14af1cc
b0d7c52
368d1a4
bb352e1
8b63aa8
39858e7
39a777e
0ea720f
6c1aa84
2b160de
3b390fc
c84e80c
e312403
86926bd
1ef08db
48f7857
04a451f
187c75f
88b8dbc
aa3d30c
38f9e68
b1c73f8
8f7b6b7
943532c
08b75fe
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 67 in providers/base/bin/v4l2_compliance_test.py
providers/base/bin/v4l2_compliance_test.py#L67
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.
Do you think we need a templated job for this?
In my case, it creates 60+ jobs. This is not inherently bad, but I don't see the point of having them as separate jobs. The output of the test is quite straightforward, and having all of these separated tests will involve more scrolling during test review, and maybe missing some other important results.
As I said, that's a minor issue if there was an advantage of having there in separate jobs, but I think a joint report for all the compliance tests in one file will be better
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 used templated job for this mostly because we aren't 100% sure which ioctls are actual cert-blockers and which ones aren't. On 22.04 cameras (including USB ones that typically don't break) can fail 1 or 2 tests but the camera will appear fully functional for everyday use. Each ubuntu version also produces slightly different results for the same functioning camera. Therefore having the job templated can help us eliminate non-cert-blockers later on by filtering them out in the resource job or move them to a separate template job specifically for non-cert-blockers.
It also helps with opening/managing v4l2 bug reports since each report is related to only 1 ioctl. We don't have to read the entire jira card to see which ioctl have been fixed, which one was skipped, which one was rejected by ODM, etc.
Let me know if you think this approach makes sense. Thanks!
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.
Btw if the number of jobs is a concern maybe we could group some of the ioctls in the resource job? Instead of creating 1 job per ioctl, we could do 1 job per category given by v4l2-compliance. For example instead of 7 jobs we can have just 2 (Codec ioctl job and Buffer ioctl job)

It would look something like this