-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
tests: increase memory size for webcam viewing VM #28
base: master
Are you sure you want to change the base?
Conversation
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2024100113-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2024091704-4.3&flavor=update
Failed tests16 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/112766#dependencies 199 fixed
Unstable tests
|
This does not help. With I've tried also another approach to the webcam test: use |
Handle timeout waiting for the device as test failure earlier.
a54d6de
to
4f75f75
Compare
vivid is an upstream v4l2 device for userspace testing, so it should fit perfectly for this case. It appears to be more reliable than v4l2loopback. The only issue is the produced video is dynamic (it has timestamp rendered on it), so capturing it at source and destination leads to a slightly different results. I haven't found any option to disable timestamp, so apply a mask before comparing images. Additionally, compare I420 images, to avoid (loosy) conversion to RGB and back.
Those aren't supported here, so ignore them explicitly, instead of falling back into noisy catch-all statement.
It's blacklisted on Whonix, so skip the test there.
Avoid 'Failed to allocate a buffer' error. In practice, that VM will run
some more apps so won't be at minimum memory anyway.