-
Notifications
You must be signed in to change notification settings - Fork 662
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
motioneye_init: stop and disable conflicting motion.service #2980
Conversation
The motion package installs a motion systemd service, which can block camera devices and hence conflict with the motionEye-controlled motion processes. We hence need to assure that this service is stopped and disabled, before we can start and enable out motioneye.service. Signed-off-by: MichaIng <[email protected]>
Signed-off-by: MichaIng <[email protected]>
I am not sure why this test suddenly runs into errors, on a totally unrelated (no Python code) commit. I guess pytest or some dependency god a breaking update. The log talks about non-defined runTest method, which is the default method called by tornado.test classes. But I think the underlying issue is some incompatible variables types, see mypy test errors (which we ignore as well). I hope someone with pytest experience can look into it. Probably those tests should be built up from scratch anyway. Until then, we ignore the errors, like we do for MJPEG and RTMP tests already. Signed-off-by: MichaIng <[email protected]>
If someone is able to identify the issue with the |
There is no point to test on different Ubuntu versions, when we use the same Python version on all of them. Use the Python version that is used on the respective Ubuntu version explicitly. The runners ship with the same minor version (3.8, 3.10 etc), but with more recent patch versions than provided by the Ubuntu APT repositories. Signed-off-by: MichaIng <[email protected]>
I wonder if the test failure is related to this: tornadoweb/tornado#3374 At least downgrading pytest to 8.1.2 as mentioned here seems to fix the issue. |
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.
The actual change (disabling the conflicting service) looks ok to me 👍
Great find, yes that will be it. I subscribed to the PR and will un-ignore the tests, once it was merged and released. |
The motion package installs a motion systemd service, which can block camera devices and hence conflict with the motionEye-controlled motion processes.
We hence need to assure that this service is stopped and disabled, before we can start and enable our motioneye.service.
See #2810 (comment), #2816 and other cases.