Closed jarylc closed 9 months ago
They merged a PR upstream that has completely broken their networking config and nobody seems to have noticed/cared, but it's causing our CI tests to fail.
Ah, I see. I didn't check the Jenkins logs.
Seems more of an upstream issue in that case, shall I leave this issue open to track this?
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Upstream issue https://github.com/jellyfin/jellyfin/issues/10070
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
closing as we do not offer support for our nightly tags and this is an upstream issue but was also resolved by upstream 14 hours ago.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
Expected Behavior
Nightly builds should continue
Steps To Reproduce
Not applicable
Environment
CPU architecture
x86-64
Docker creation
Container logs