Skip to content
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

Merged
merged 5 commits into from
May 11, 2024

Conversation

MichaIng
Copy link
Member

@MichaIng MichaIng commented May 9, 2024

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.

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]>
@MichaIng MichaIng added the bug label May 9, 2024
@MichaIng MichaIng added this to the v0.43.1 milestone May 9, 2024
@MichaIng MichaIng requested a review from zagrim May 9, 2024 15:49
MichaIng added 2 commits May 9, 2024 20:43
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]>
@MichaIng
Copy link
Member Author

MichaIng commented May 9, 2024

If someone is able to identify the issue with the test_python test, that would be great. See the commit message where I ignore their outcome. The logs are of course still there, even when the result is green. I guess the true error is to be found in the mypy test before the pytest failure, about incompatible variable types in the test classes. In any case, it is an issue with the test itself, not with the code it tests.

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]>
@zagrim
Copy link
Collaborator

zagrim commented May 11, 2024

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.

Copy link
Collaborator

@zagrim zagrim left a 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 👍

@MichaIng
Copy link
Member Author

Great find, yes that will be it. I subscribed to the PR and will un-ignore the tests, once it was merged and released.

@MichaIng MichaIng merged commit ffe0be0 into dev May 11, 2024
16 checks passed
@MichaIng MichaIng deleted the fix-motion-service branch May 11, 2024 12:19
This was referenced May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

Camera reconnected, videos are generated but the dashboard shows "Unable to open video device"
2 participants