mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Unit tests are failing after EFCore migration #6688
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jsoref on GitHub (Jan 27, 2025).
This issue respects the following points:
Description of the bug
Master CI is failing on a couple of tests
Reproduction steps
What is the current bug behavior?
What is the expected correct behavior?
Jellyfin Server version
Master
Specify commit id
7e9ce78849Specify unstable release number
No response
Specify version number
No response
Specify the build version
?
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
This commit would bypass the failing tests:
0c23622527@gnattu commented on GitHub (Jan 27, 2025):
macOS fails first because its is running the test fastest but the problem failing the CI is not platform specific, it is efcore migration is still unstable.
@jsoref commented on GitHub (Jan 27, 2025):
@gnattu commented on GitHub (Jan 27, 2025):
A fail is a fail, playing with the ci not make it looks good makes no sense.
@JPVenson commented on GitHub (Mar 28, 2025):
This issue has been mitigated by pr #13765 but the underlying issue has not been resolved.
The offending tests are now ignored and will stay that way until they are either fixed on the GH piplines or intigration tests are properly rewritten in whole.
Leaving this open for now as the issue technically still exists
@jsoref commented on GitHub (Mar 28, 2025):
@jellyfin-bot commented on GitHub (Jul 27, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jsoref commented on GitHub (Jul 27, 2025):
.